From: Jeff Layton <jlayton@redhat.com>
To: bfields@fieldses.org
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/3] sunrpc: have pooled services make NUMA-friendly allocations
Date: Fri, 6 Jun 2008 11:21:45 -0400 [thread overview]
Message-ID: <20080606112145.6a23afca@tleilax.poochiereds.net> (raw)
In-Reply-To: <20080603111802.8769.22921.stgit@dantu.usersys.redhat.com>
On Tue, 03 Jun 2008 07:18:02 -0400
Jeff Layton <jlayton@redhat.com> wrote:
> Currently, svc_prepare_thread allocates memory using plain kmalloc()
> and alloc_page() calls, even for threads that are destined to run on
> different CPUs or NUMA nodes than the current one. Add a function to
> translate a poolid into a NUMA node, and have svc_prepare_thread and
> svc_init_buffer allocate memory on those nodes instead.
>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
--------[snip]--------
>
> - rqstp = kzalloc(sizeof(*rqstp), GFP_KERNEL);
> + rqstp = kzalloc_node(sizeof(*rqstp), GFP_KERNEL, node);
Bruce,
It looks like AKPM has taken the kzalloc_node patch into -mm. I'd
like to have you take this set into your tree at some point, but don't
want you to have to carry that VM patch too. Would you be amenable to me
changing the above to something like:
/* FIXME: change to kzalloc_node when/if it makes it to mainline */
rqstp = kmalloc_node(sizeof(*rqstp), GFP_KERNEL | __GFP_ZERO, node);
...and then we can make the FIXME change when mainline has the new inline?
Thanks,
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2008-06-06 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 11:17 [PATCH 1/3] VM: add kzalloc_node inline Jeff Layton
2008-06-03 11:18 ` [PATCH 2/3] sunrpc: have pooled services make NUMA-friendly allocations Jeff Layton
2008-06-06 15:21 ` Jeff Layton [this message]
2008-06-06 15:41 ` J. Bruce Fields
2008-06-03 11:18 ` [PATCH 3/3] sunrpc: change default for pooled services to SVC_POOL_AUTO and make settings persistent Jeff Layton
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=20080606112145.6a23afca@tleilax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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
all inboxes | Powered by JetHome®