linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: Nick Piggin <npiggin@suse.de>
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 13:04:10 +0000	[thread overview]
Message-ID: <20081202130410.GA24222@totally.trollied.org.uk> (raw)
In-Reply-To: <20081202070608.GA28080@wotan.suse.de>

On Tue, Dec 02, 2008 at 08:06:08AM +0100, Nick Piggin wrote:

> > Don't you even have a differential profile showing the impact of
> > removing d_cookie? This hash table lookup will now happen on *every*
> > userspace sample that's processed. That's, uh, a lot.
> 
> I don't know what you mean by every sample that's processed, but
> won't the hash lookup only happen for the *first* time that a given
> name is asked for a dcookie (ie. fast_get_dcookie, which, as I said,
> should actually be moved to fs/dcookies.c)

I mis-read your changes.

> > (By all means make your change, but I don't get how it's OK to regress
> > other code, and provide no evidence at all as to its impact.)
> 
> Tradeoffs are made all the time. This is obviously a good one, and
                                           ^^^^^^^^^^^^^^^^^^^^

By all means make your change, but I don't get how it's OK to regress
other code, and provide no evidence at all as to its impact.

> I provided evidence of the impact of the improvement in the common
> case. I also acknowledge it can slow down the uncommon case, but
> showed ways that can easily be improved. Do you want me to just try
> to make an artificial case where I mmap thousands of tiny shared
> libraries and try to overflow the hash and try to detect a difference?

You haven't even bothered to show that it hasn't affected normal
oprofile use yet.

I can't believe I'm having to argue that you need to test your code. So
I think I'll stop.

> Did you add d_cookie? If so, then surely at the time you must have

It was added along with the rest of oprofile, so I don't have breakout
numbers. I did have oprofile overhead numbers, though I doubt I could
find them now.

john

--
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>

  reply	other threads:[~2008-12-02 13:04 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 [this message]
2008-12-02 13:49           ` Nick Piggin
2008-12-02 14:49             ` John Levon
2008-12-02 15:11               ` Nick Piggin

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=20081202130410.GA24222@totally.trollied.org.uk \
    --to=levon@movementarian.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --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