sorry....my previous was accidentally sent out halfway...specifically detailing on the implementation of drop_caches_sysctl_handler(): > and reading into the implementation, it just wipe away all the dirty > buffer cache (as the name implies). Not really the type of flushing > I originally meant - which is to write back the dirty buffer cache to > the backing store. > drop_caches_sysctl_handler()---> drop_pagecache()--->drop_pagecache_sb()--->invalidate_mapping_pages(). where invalidate_mappping_pages() is in mm/truncate.c.....and so on. and as drop_pagecache_sb() is done for each filesystem's superblock, which is why my initial statement is that it is performance-heavy. if u know what to flush out, doing it directly will be much better. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
