Wez Furlong fe1a376e0f migrate functionScheduler to eventBase timer ... 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		2017-09-13 08:42:21 -07:00
..
config	Re-run autodeps on all TARGETS	2017-09-09 18:35:02 -07:00
fuse	record number of fuse requests in the Dispatcher	2017-09-08 19:25:34 -07:00
inodes	Introduce a special NoValueForKeyError for hgGetDirstateTuple() and hgCopyMapGet().	2017-09-11 10:52:09 -07:00
journal	fix journal merging of remove followed by create events	2017-08-17 12:33:51 -07:00
model	Re-run autodeps on all TARGETS	2017-09-09 18:35:02 -07:00
rocksdb	use rocksdb column families to separate key spaces	2017-09-07 14:50:42 -07:00
service	migrate functionScheduler to eventBase timer	2017-09-13 08:42:21 -07:00
store	use rocksdb column families to separate key spaces	2017-09-07 14:50:42 -07:00
testharness	Re-run autodeps on all TARGETS	2017-09-09 18:35:02 -07:00
utils	Modification of unloadChildrenNow	2017-08-18 14:20:43 -07:00