From: Mike Waychison <mikew@google.com>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v1 1/8] Deferred batching of dput()
Date: Tue, 20 Jan 2009 12:07:13 -0800 [thread overview]
Message-ID: <49762EF1.3000001@google.com> (raw)
In-Reply-To: <20090117101501.GA2682@ioremap.net>
Evgeniy Polyakov wrote:
> Hi Mike.
>
> On Fri, Jan 16, 2009 at 06:29:42PM -0800, Mike Waychison (mikew@google.com) wrote:
>> +static void postpone_dput(struct dentry *dentry)
>> +{
>> + struct postponed_dentries *ppd, *new_ppd;
>> +
>> +again:
>> + ppd = get_cpu_var(postponed_dentries);
>> + if (!pending_dput_full(ppd)) {
>> + add_pending_dput(ppd, dentry);
>> + put_cpu_var(postponed_dentries);
>> + return;
>> + }
>> +
>> + /* need to flush out existing pending dentries. */
>> + put_cpu_var(postponed_dentries);
>> + /* Allocate more space.. */
>> + new_ppd = new_postponed_dentries();
>> + if (!new_ppd) {
>> + /* Take the slow path, memory is low */
>> + struct postponed_dentries_onstack ppd_onstack;
>> + struct postponed_dentries *ppd;
>> +
>> + ppd = init_ppd_onstack(&ppd_onstack);
>> + add_pending_dput(ppd, dentry);
>> + process_postponed_dentries(ppd);
>> + return;
>> + }
>
> Why don't you want just to put the dentry in the lowmem condition?
>
You're right. This path could just use the original dput path. I'll
fix it up in the next version.
next prev parent reply other threads:[~2009-01-20 20:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 2:29 [PATCH v1 0/8] Deferred dput() and iput() -- reducing lock contention Mike Waychison
2009-01-17 2:29 ` [PATCH v1 1/8] Deferred batching of dput() Mike Waychison
2009-01-17 10:15 ` Evgeniy Polyakov
2009-01-20 20:07 ` Mike Waychison [this message]
2009-01-17 2:29 ` [PATCH v1 2/8] Parallel dput() Mike Waychison
2009-01-17 2:29 ` [PATCH v1 3/8] Deferred batching of iput() Mike Waychison
2009-01-17 10:18 ` Evgeniy Polyakov
2009-01-20 20:07 ` Mike Waychison
2009-01-17 2:29 ` [PATCH v1 4/8] Fixing iput() called from put_super path Mike Waychison
2009-01-17 2:30 ` [PATCH v1 5/8] Parallelize iput() Mike Waychison
2009-01-17 2:30 ` [PATCH v1 6/8] hugetlbfs drop_inode update Mike Waychison
2009-01-17 2:30 ` [PATCH v1 7/8] Make drop_caches flush pending dput()s and iput()s Mike Waychison
2009-01-17 2:30 ` [PATCH v1 8/8] Make the sync path drain dentries and inodes Mike Waychison
2009-01-17 7:04 ` [PATCH v1 0/8] Deferred dput() and iput() -- reducing lock contention Eric Dumazet
2009-01-20 20:00 ` Mike Waychison
2009-01-17 8:12 ` Dave Chinner
2009-01-20 19:01 ` Mike Waychison
2009-01-29 2:09 ` Mike Waychison
2009-01-21 5:52 ` Andi Kleen
2009-01-21 6:22 ` Mike Waychison
2009-01-21 8:48 ` Andi Kleen
2009-01-21 17:28 ` Mike Waychison
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=49762EF1.3000001@google.com \
--to=mikew@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zbr@ioremap.net \
/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
Powered by JetHome