On 22 December 2014 at 09:28, Konstantin Belousov <kostik...@gmail.com> wrote: > On Mon, Dec 22, 2014 at 09:40:02AM -0500, John Baldwin wrote: >> On Sunday, December 21, 2014 11:21:17 am Andriy Gapon wrote: >> > On 21/12/2014 17:14, Konstantin Belousov wrote: >> > > On Sun, Dec 21, 2014 at 04:45:28PM +0200, Andriy Gapon wrote: >> > >> On 21/12/2014 16:41, Konstantin Belousov wrote: >> > >>> Or, are you asking why caching of the name could be needed for >> > >>> core dump files at all ? >> > >> >> > >> Sort of. Why VN_OPEN_NAMECACHE is useful in the case of core dumps? >> > >> What does it make better? >> > > The vn_fullpath() mostly works for the core files after the change, >> > > comparing with the non-working state at all before. >> > > >> > >> > Ah, vn_fullpath(). Thank you. >> >> Is there something specific to core dumps that makes vn_fullpath() more >> useful to have working before a process tries to open the core? (As >> compared to other newly-created files) > > See other Rui' reply in the thread. It was done by his request. > > Basically, we cannot enable caching for CREATE, since operations like > extracting large archive, would flush the cache. Doing it rarely > and when needed is acceptable. The explained use case seems to > be warranted.
.. 2c, sounds like having an ARC style replacement policy for namecache entries would be useful. (I mean the policy as described in the ARC paper, not the ZFS implementation as a block cache.) -adrian _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
