From: Christoph Hellwig <hch@sgi.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-fsdevel@vger.kernel.org
Subject: keeping nfsd dentries on unused_list
Date: Mon, 21 Oct 2002 17:37:53 -0400 [thread overview]
Message-ID: <20021021173753.A15099@sgi.com> (raw)
Hi Neil,
since your export changes in 2.5.<early> always have a non-empty
->d_hash (linked into sb->s_anon) and thus are put on the unused
list by dput instead of directly reclaiming it.
Is this behaviour intentional and will stay during 2.6? Keeping
those dentries alive will allow me to remove lots of code in XFS
to keep inodes that are written to by nfsd in cache as the final
iput will flush all delayed allocated space and thus decrease
nfs write performance massively - but as long as the dentry is
on the unused list after dput we still have an inode reference
and thus the delalloc block don't need to be converted.
next reply other threads:[~2002-10-21 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 21:37 Christoph Hellwig [this message]
2002-10-21 23:15 ` keeping nfsd dentries on unused_list Neil Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021021173753.A15099@sgi.com \
--to=hch@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).