From: Josef Bacik <josef@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] Btrfs: load the key from the dir item in readdir into a fake dentry
Date: Thu, 26 May 2011 15:02:42 -0400 [thread overview]
Message-ID: <4DDEA3D2.3080907@redhat.com> (raw)
In-Reply-To: <m2fwo19tzp.fsf@firstfloor.org>
On 05/26/2011 02:50 PM, Andi Kleen wrote:
> Josef Bacik <josef@redhat.com> writes:
>> +
>> + newkey = kzalloc(sizeof(struct btrfs_key),
>> + GFP_NOFS);
>> + if (!newkey)
>> + goto no_dentry;
>> + tmp = d_alloc(filp->f_dentry, &q);
>
> This doesn't seem to address the "find / fills all memory with dentries"
> concerns brought up earlier at all.
>
Nope, this part does in patch 1/1
+ /*
+ * If this dentry needs lookup, don't set the referenced flag so that it
+ * is more likely to be cleaned up by the dcache shrinker in case of
+ * memory pressure.
+ */
+ if (!d_need_lookup(dentry))
+ dentry->d_flags |= DCACHE_REFERENCED;
> d_alloc uses a normal GFP_KERNEL, which is quite in appropiate for this.
>
> It should at least reclaim and probably more, but even then it's
> risky.
>
Ah yeah I guess I should have probably used GFP_KERNEL. Sorry about that,
Josef
next prev parent reply other threads:[~2011-05-26 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <adilger@dilger.ca, hch@lst.de>
2011-05-26 14:48 ` [PATCH 1/2] fs: add a DCACHE_NEED_LOOKUP flag for d_flags Josef Bacik
2011-05-26 14:48 ` [PATCH 2/2] Btrfs: load the key from the dir item in readdir into a fake dentry Josef Bacik
2011-05-26 18:50 ` Andi Kleen
2011-05-26 19:02 ` Josef Bacik [this message]
2011-05-26 20:03 ` Andi Kleen
2011-05-26 20:18 ` Josef Bacik
2011-05-26 20:45 ` Andreas Dilger
2011-05-19 17:58 [PATCH 1/2] fs: add a DCACHE_NEED_LOOKUP flag for d_flags Josef Bacik
2011-05-19 17:58 ` [PATCH 2/2] Btrfs: load the key from the dir item in readdir into a fake dentry Josef Bacik
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=4DDEA3D2.3080907@redhat.com \
--to=josef@redhat.com \
--cc=andi@firstfloor.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
/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).