From: Andrew Morton <akpm@linux-foundation.org>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
sct@redhat.com, adilger@clusterfs.com, clameter@sgi.com
Subject: Re: [RFC/PATCH] ext3: remove inode constructor
Date: Sat, 5 May 2007 02:02:02 -0700 [thread overview]
Message-ID: <20070505020202.8edd0110.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705051156200.20079@sbz-30.cs.Helsinki.FI>
On Sat, 5 May 2007 11:58:45 +0300 (EEST) Pekka J Enberg <penberg@cs.helsinki.fi> wrote:
> On Fri, 4 May 2007, Andrew Morton wrote:
> > I got 100% rejects against this because Christoph has already had
> > his paws all over the slab constructor code everywhere.
> >
> > Was going to fix it up but then decided that we ought to make changes
> > like this to ext4 as well. Ideally beforehand, but simultaneously is
> > OK as long as it's simple enough.
>
> I'll send you proper patches for them (and will convert other filesystems
> too).
May as well.
> On Fri, 4 May 2007, Andrew Morton wrote:
> > btw, for a benchmark I'd suggest just a silly create-10000-files
> > tight loop rather than something more complex like postmark.
>
> Do you want me to redo the benchmarks or are you happy enough with the
> postmark numbers?
I doubt if this is measurable, really. It'll be something like the
difference between an L1 hit and an L2 hit in amongst all the other stuff
we do on a per-inode basis.
next prev parent reply other threads:[~2007-05-05 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 10:14 [RFC/PATCH] ext3: remove inode constructor Pekka J Enberg
2007-05-04 16:08 ` Christoph Lameter
2007-05-05 9:21 ` Pekka J Enberg
2007-05-04 20:02 ` Andrew Morton
2007-05-05 8:58 ` Pekka J Enberg
2007-05-05 9:02 ` Andrew Morton [this message]
2007-05-05 9:08 ` Pekka J Enberg
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=20070505020202.8edd0110.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adilger@clusterfs.com \
--cc=clameter@sgi.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=sct@redhat.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 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.