From: Eric Sandeen <sandeen@redhat.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] use percpu data for lg_prealloc_list
Date: Mon, 18 Aug 2008 11:07:57 -0500 [thread overview]
Message-ID: <48A99E5D.2020309@redhat.com> (raw)
In-Reply-To: <20080818155650.GA6491@skywalker>
Aneesh Kumar K.V wrote:
> On Mon, Aug 18, 2008 at 10:47:40AM -0500, Eric Sandeen wrote:
>> Eric Sandeen wrote:
>>> lg_prealloc_list seems to cry out for a per-cpu data structure; on a large
>>> smp system I think this should be better. I've lightly tested this change
>>> on a 4-cpu system. Comments welcome...
>> Any thoughts on this? Does this seem to be the right way to go?
>>
>
> Acked-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Thanks :) I'll toss it in the patch queue.
-Eric
prev parent reply other threads:[~2008-08-18 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 19:11 [PATCH] use percpu data for lg_prealloc_list Eric Sandeen
2008-08-18 15:47 ` Eric Sandeen
2008-08-18 15:56 ` Aneesh Kumar K.V
2008-08-18 16:07 ` Eric Sandeen [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=48A99E5D.2020309@redhat.com \
--to=sandeen@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
/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