mirror of
https://github.com/facebook/sapling.git
synced 2024-10-08 07:49:11 +03:00
fe1a376e0f
Summary: This is reasonably straightforward, although a little more fiddly than I'd hoped because the timer wheel stuff doesn't offer a convenient way to set up a recurring timer. I've also made the inode unloading code get run globally for all mounts; it was previously scheduling one timer per mount point. This nets out the same; the function scheduler was just a single thread anyway, so there is no change in the level of concurrency. I believe that this tidies up the unload counter too; it looked like we'd set the counter to be the result of the last mount point that we processed rather than the aggregate of all mounts. Having the unload timer be associated with the server rather than the mount points means that we don't have to do anything special to coordinate with the timer management when the mount point is being torn down. Reviewed By: bolinfest Differential Revision: D5792938 fbshipit-source-id: 1a14bb7b7f4952139e684fe6b52f64bd1ba70dd0 |
||
|---|---|---|
| .. | ||
| cli | ||
| docs | ||
| fs | ||
| hooks | ||
| integration | ||
| DEFS | ||