From: Jack Steiner <steiner@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Andrea Arcangeli <andrea@suse.de>,
paulmck@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: RCU scaling on large systems
Date: Tue, 18 May 2004 08:33:05 -0500 [thread overview]
Message-ID: <20040518133305.GA4848@sgi.com> (raw)
In-Reply-To: <20040517144228.7172d681.akpm@osdl.org>
On Mon, May 17, 2004 at 02:42:28PM -0700, Andrew Morton wrote:
> Andrea Arcangeli <andrea@suse.de> wrote:
> >
> > On Fri, May 07, 2004 at 04:32:35PM -0700, Andrew Morton wrote:
> > > Jack Steiner <steiner@sgi.com> wrote:
> > > >
> > > > The calls to RCU are coming from here:
> > > >
> > > > [11]kdb> bt
> > > > Stack traceback for pid 3553
> > > > 0xe00002b007230000 3553 3139 1 11 R 0xe00002b0072304f0 *ls
> > > > 0xa0000001000feee0 call_rcu
> > > > 0xa0000001001a3b20 d_free+0x80
> > > > 0xa0000001001a3ec0 dput+0x340
> > > > 0xa00000010016bcd0 __fput+0x210
> > > > 0xa00000010016baa0 fput+0x40
> > > > 0xa000000100168760 filp_close+0xc0
> > > > 0xa000000100168960 sys_close+0x180
> > > > 0xa000000100011be0 ia64_ret_from_syscall
> > > >
> > > > I see this same backtrace from numerous processes.
> > >
> > > eh? Why is dput freeing the dentry? It should just be leaving it in cache.
> > >
> > > What filesystem is being used? procfs?
> >
> > deleting entries from dcache can be a frequent operation, even rename()
> > triggers d_free.
>
> This issue has gone all quiet. Is anyone doing aything?
I plan to look into the RCU scaling issues (unless someone beats me to
it) but it will be a couple of weeks before I can start.
>
> > note that I changed my tree to free all negative entries that are
> > currently generated by unlink. I find useless to leave negative dentries
> > after "unlink". I leave them of course after a failed lookup (that's the
> > fundamental usage of the negative dentries for the PATHs userspace
> > lookups), but not after unlink.
>
> Sounds sensible. Could you please send out the patch?
>
> > RCU basically trades mugh higher performance for reader, with much lower
> > performance for the writer.
>
> If the writer wants synchronous-removal semantics, yes.
>
> The problem here and, I believe, in the route cache is in finding a balance
> between the amount of storage and the frequency of RCU callback runs.
--
Thanks
Jack Steiner (steiner@sgi.com) 651-683-5302
Principal Engineer SGI - Silicon Graphics, Inc.
next prev parent reply other threads:[~2004-05-18 13:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 12:08 RCU scaling on large systems Jack Steiner
2004-05-01 21:17 ` William Lee Irwin III
2004-05-01 22:35 ` William Lee Irwin III
2004-05-02 1:38 ` Jack Steiner
2004-05-07 17:53 ` Andrea Arcangeli
2004-05-07 18:17 ` William Lee Irwin III
2004-05-07 19:59 ` Andrea Arcangeli
2004-05-07 20:49 ` Jack Steiner
2004-05-02 18:28 ` Paul E. McKenney
2004-05-03 16:39 ` Jesse Barnes
2004-05-03 20:04 ` Paul E. McKenney
2004-05-03 18:40 ` Jack Steiner
2004-05-07 20:50 ` Paul E. McKenney
2004-05-07 22:06 ` Jack Steiner
2004-05-07 23:32 ` Andrew Morton
2004-05-08 4:55 ` Jack Steiner
2004-05-17 21:18 ` Andrea Arcangeli
2004-05-17 21:42 ` Andrew Morton
2004-05-17 23:50 ` Andrea Arcangeli
2004-05-18 13:33 ` Jack Steiner [this message]
2004-05-18 23:13 ` Matt Mackall
-- strict thread matches above, loose matches on Subject: below --
2004-05-20 11:36 Manfred Spraul
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=20040518133305.GA4848@sgi.com \
--to=steiner@sgi.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
/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