From: Huang Ying <ying.huang@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH -mm -v8 0/3] Lockless memory allocator and list
Date: Fri, 17 Dec 2010 08:20:32 +0800 [thread overview]
Message-ID: <1292545232.12648.1236.camel@yhuang-dev> (raw)
In-Reply-To: <1292491467.6803.4327.camel@twins>
On Thu, 2010-12-16 at 17:24 +0800, Peter Zijlstra wrote:
> On Thu, 2010-12-16 at 14:59 +0800, Huang Ying wrote:
> > This patchset adds a lockless memory allocator and a lock-less
> > list.
>
> Still no users the allocator, and no attempt to unify the existing
> lockless list implementations.
>
> I'm getting very tired of this Huang.
I just want to do that in the next step after merging the data structure
itself. The first user of the allocator is APEI, which will go ACPI
tree, lockless list in irq_work will go tip tree, lockless list in xlist
will go net tree.
We must merge the data structure with its users together?
Best Regards,
Huang Ying
next prev parent reply other threads:[~2010-12-17 0:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 6:59 [PATCH -mm -v8 0/3] Lockless memory allocator and list Huang Ying
2010-12-16 6:59 ` [PATCH -mm -v8 1/3] Add Kconfig option ARCH_HAVE_NMI_SAFE_CMPXCHG Huang Ying
2010-12-16 6:59 ` [PATCH -mm -v8 2/3] lib, Make gen_pool memory allocator lockless Huang Ying
2010-12-16 6:59 ` [PATCH -mm -v8 3/3] lib, Add lock-less NULL terminated single list Huang Ying
2010-12-16 9:24 ` [PATCH -mm -v8 0/3] Lockless memory allocator and list Peter Zijlstra
2010-12-17 0:20 ` Huang Ying [this message]
2010-12-17 12:22 ` Peter Zijlstra
2010-12-17 15:35 ` huang ying
2010-12-17 16:22 ` Thomas Gleixner
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=1292545232.12648.1236.camel@yhuang-dev \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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