From: Nick Piggin <npiggin@suse.de>
To: John Levon <levon@movementarian.org>
Cc: linux-fsdevel@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>,
robert.richter@amd.com, oprofile-list@lists.sf.net
Subject: Re: [patch][rfc] fs: shrink struct dentry
Date: Tue, 2 Dec 2008 16:11:42 +0100 [thread overview]
Message-ID: <20081202151141.GC3235@wotan.suse.de> (raw)
In-Reply-To: <20081202144918.GB24222@totally.trollied.org.uk>
On Tue, Dec 02, 2008 at 02:49:18PM +0000, John Levon wrote:
> On Tue, Dec 02, 2008 at 02:49:26PM +0100, Nick Piggin wrote:
>
> > > I can't believe I'm having to argue that you need to test your code. So
> > > I think I'll stop.
> >
> > Code was tested. It doesn't affect my normal oprofile usage (it's
> > utterly within the noise, in case that wasn't obvious to you).
>
> Then, heck, why didn't you say so?! I just went and read the whole
> exchange and this is the first time you actually stated you tested the
> impact of your patch on oprofile overhead.
This was just in running some silly benchmark like oprofile+tbench,
but I'm fairly sure it a) probably didn't have many entries in the
cookies cache -- at least not enough to create big hash chains, and
b) wasn't hitting get_dcookie very often, and c) AFAIKS, all paths to
get_dcookie go through fast_get_dcookie so I actually can't see any
possible way that this patch could increase the number of hash lookups
anyway.
Given that, I was 99.9% sure it will be OK. But I like confirmation
from you.
I didn't do any major test where I try to force thousands of entries
into dcookie subsystem or anything, but if you care to give a test
case I can try.
mmap_sem and find_vma is much more annoying in oprofile :) Speaking of
which: is there a mode it can be set in to do kernel only profiling so
it does not bother with userspace samples at all? That would be really
nice for profiling the kernel in the kinds of workloads that hit
mmap_sem and vma cache often because oprofile interferes with that.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2008-12-02 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 8:33 Nick Piggin
2008-12-01 11:09 ` Andi Kleen
2008-12-01 11:26 ` Nick Piggin
2008-12-01 17:51 ` John Levon
2008-12-01 18:04 ` Nick Piggin
2008-12-01 19:38 ` John Levon
2008-12-02 7:06 ` Nick Piggin
2008-12-02 13:04 ` John Levon
2008-12-02 13:49 ` Nick Piggin
2008-12-02 14:49 ` John Levon
2008-12-02 15:11 ` Nick Piggin [this message]
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=20081202151141.GC3235@wotan.suse.de \
--to=npiggin@suse.de \
--cc=levon@movementarian.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oprofile-list@lists.sf.net \
--cc=robert.richter@amd.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