From: Waiman Long <waiman.long@hp.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Simo Sorce <simo@redhat.com>, Dave Chinner <david@fromorbit.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jeff Layton <jlayton@redhat.com>,
Miklos Szeredi <mszeredi@suse.cz>, Ian Kent <raven@themaw.net>,
Sage Weil <sage@inktank.com>, Steve French <sfrench@samba.org>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Eric Paris <eparis@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
autofs@vger.kernel.org, ceph-devel@vger.kernel.org,
linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org,
"Chandramouleeswaran, Aswin" <aswin@hp.com>,
"Norton, Scott J" <scott.norton@hp.com>
Subject: Re: [PATCH 0/3 v3] dcache: make it more scalable on large system
Date: Wed, 29 May 2013 16:37:21 -0400 [thread overview]
Message-ID: <51A66701.6050104@hp.com> (raw)
In-Reply-To: <20130529165603.GL6123@two.firstfloor.org>
On 05/29/2013 12:56 PM, Andi Kleen wrote:
> On Wed, May 29, 2013 at 12:18:09PM -0400, Simo Sorce wrote:
>> To be honest a workload base on /etc/passwd or /etc/group is completely
>> artificial, in actual usage, if you really have such access you use
>> nscd or sssd with their shared memory caches to completely remove most
>> of the file access.
> I don't fully agree at this point. A lot of things can be tuned away,
> but in practice we want things to perform well out of the box without
> needing all kinds of magic tuning that only
>
> Also this is just normal file access, nothing special about it.
> It simply has to scale. For all kinds of workloads.
>
> And it does, just d_path messes it up.
Just for clarification, the AIM7 workload is not affected by the current
d_path() code, they are speed-limited by the lock contention in the
dcache reference counting code. However, both the d_path() change and
the dentry reference counting change are needed to to eliminate the
overhead introduced by the use of the perf-record command.
Regards,
Longman
next prev parent reply other threads:[~2013-05-29 20:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 1:37 [PATCH 0/3 v3] dcache: make it more scalable on large system Waiman Long
2013-05-23 1:37 ` [PATCH 1/3 v3] dcache: Don't take unnecessary lock in d_count update Waiman Long
2013-05-23 1:37 ` Waiman Long
2013-05-23 1:37 ` Waiman Long
2013-05-23 1:37 ` [PATCH 2/3 v3] dcache: introduce a new sequence read/write lock type Waiman Long
2013-05-23 1:37 ` Waiman Long
2013-05-23 1:37 ` Waiman Long
2013-05-23 1:37 ` [PATCH 3/3 v3] dcache: change rename_lock to a sequence read/write lock Waiman Long
2013-05-23 1:37 ` Waiman Long
2013-05-23 1:37 ` Waiman Long
2013-05-23 9:42 ` [PATCH 0/3 v3] dcache: make it more scalable on large system Dave Chinner
2013-05-23 21:34 ` Waiman Long
2013-05-23 21:34 ` Waiman Long
2013-05-27 2:09 ` Dave Chinner
2013-05-29 15:55 ` Waiman Long
[not found] ` <51A624E2.3000301-VXdhtT5mjnY@public.gmane.org>
2013-05-29 16:13 ` Andi Kleen
2013-05-29 16:13 ` Andi Kleen
[not found] ` <20130529161358.GJ6123-1g7Xle2YJi4/4alezvVtWx2eb7JE58TQ@public.gmane.org>
2013-05-29 20:23 ` Waiman Long
2013-05-29 20:23 ` Waiman Long
2013-05-29 16:18 ` Simo Sorce
2013-05-29 16:18 ` Simo Sorce
2013-05-29 16:56 ` Andi Kleen
2013-05-29 17:03 ` Simo Sorce
2013-05-29 20:37 ` Waiman Long [this message]
[not found] ` <1369844289.2769.146.camel-Hs+ccMQdwurzDu64bZtGtWD2FQJk+8+b@public.gmane.org>
2013-05-29 20:32 ` Waiman Long
2013-05-29 20:32 ` Waiman Long
2013-05-29 18:46 ` J. Bruce Fields
2013-05-29 18:46 ` J. Bruce Fields
2013-05-29 20:37 ` Andi Kleen
[not found] ` <20130529203700.GM6123-1g7Xle2YJi4/4alezvVtWx2eb7JE58TQ@public.gmane.org>
2013-05-29 20:43 ` J. Bruce Fields
2013-05-29 20:43 ` J. Bruce Fields
2013-05-29 21:01 ` Andi Kleen
2013-05-29 21:19 ` Jörn Engel
2013-05-29 21:19 ` Jörn Engel
2013-05-30 15:48 ` Waiman Long
2013-05-30 15:48 ` Waiman Long
2013-05-30 15:11 ` Jörn Engel
2013-05-30 15:11 ` Jörn Engel
2013-06-06 3:48 ` Dave Chinner
2013-05-29 20:40 ` Waiman Long
2013-05-23 1:37 Waiman Long
2013-05-23 1:37 ` Waiman Long
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=51A66701.6050104@hp.com \
--to=waiman.long@hp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=andi@firstfloor.org \
--cc=aswin@hp.com \
--cc=autofs@vger.kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=david@fromorbit.com \
--cc=eparis@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=raven@themaw.net \
--cc=sage@inktank.com \
--cc=scott.norton@hp.com \
--cc=sfrench@samba.org \
--cc=simo@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.