From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Dipankar Sarma <dipankar@in.ibm.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
"David S. Miller" <davem@davemloft.net>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/6] mm: alloc_percpu and bigrefs
Date: Fri, 23 Sep 2005 11:48:20 -0700 [thread overview]
Message-ID: <20050923184820.GB4103@localhost.localdomain> (raw)
In-Reply-To: <20050923113636.GB5006@in.ibm.com>
On Fri, Sep 23, 2005 at 05:06:36PM +0530, Dipankar Sarma wrote:
> On Fri, Sep 23, 2005 at 06:11:30PM +1000, Rusty Russell wrote:
> > On Fri, 2005-09-23 at 00:17 -0700, David S. Miller wrote:
> > Now, that said, I wanted (and wrote, way back when) a far simpler
> > allocator which only worked for GFP_KERNEL and used the same
> > __per_cpu_offset[] to fixup dynamic per-cpu ptrs as static ones. Maybe
> > not as "complete" as this one, but maybe less offensive.
>
> The GFP_ATOMIC support stuff is needed only for dst entries. However
> using per-cpu refcounters in such objects like dentries and dst entries
> are problematic and that is why I hadn't tried changing those.
> Some of the earlier versions of the allocator were simpler and I think
> we need to roll this back and do some more analysis. No GFP_ATOMIC
> support, no early use. I haven't got around to look at this
The patches I have submitted this time does not have GFP_ATOMIC support. The
early use enablement stuff are in seperate patches (patch 5 and 6). The
patchset would work without these two patches too.
Thanks,
Kiran
next prev parent reply other threads:[~2005-09-23 18:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050923062529.GA4209@localhost.localdomain>
2005-09-23 7:10 ` [patch 0/6] mm: alloc_percpu and bigrefs Andrew Morton
2005-09-23 7:17 ` David S. Miller
2005-09-23 8:11 ` Rusty Russell
2005-09-23 11:36 ` Dipankar Sarma
2005-09-23 18:48 ` Ravikiran G Thirumalai [this message]
2005-09-23 9:03 ` Eric Dumazet
2005-09-23 9:35 ` Eric Dumazet
2005-09-23 18:40 ` Ravikiran G Thirumalai
2005-09-23 18:50 ` David S. Miller
2005-09-23 23:30 ` Ravikiran G Thirumalai
2005-09-23 19:16 ` Christoph Lameter
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=20050923184820.GB4103@localhost.localdomain \
--to=kiran@scalex86.org \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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