From: Benjamin Blum <bblum@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
akpm@linux-foundation.org, containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, menage@google.com,
vda.linux@googlemail.com, mikew@google.com,
xiyou.wangcong@gmail.com, hpa@zytor.com
Subject: Re: [RFC][PATCH] flexible array implementation v4
Date: Thu, 23 Jul 2009 20:26:47 -0700 [thread overview]
Message-ID: <2f86c2480907232026v143aef06t652796b489b7ad2c@mail.gmail.com> (raw)
In-Reply-To: <20090724120811.a581eea5.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, Jul 23, 2009 at 8:08 PM, KAMEZAWA
Hiroyuki<kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Fri, 24 Jul 2009 11:02:28 +0800
> Li Zefan <lizf@cn.fujitsu.com> wrote:
>
>> Dave Hansen wrote:
>> > Remaining issues:
>> > - How should we deal with out-of-range indexes, especially
>> > in flex_array_get() which returns void*? ERR_PTR()?
>> > BUG_ON()? return NULL (current behavior)?
>> > - Should care be taken not to allow a flex_array_get() to
>> > an index where no flex_array_put() was done?
>> > - Should we decay further than just packing things into the
>> > 'base' page? Should we actually kmalloc() less than a
>> > page at times when it will fit?
>> >
>>
>> I sugguest find some candidate users and see how this flex_array
>> fits them.
>>
> Hmm, can't we rewrite cgroup->tasks file using this ?
> I'll try some if I have time.
>
> -Kame
>
>
>
I can do that; it would go nicely on top of my procs file patch
series, but probably wants to wait until after both patch series have
been accepted (see http://lkml.org/lkml/2009/7/23/330 )
next prev parent reply other threads:[~2009-07-24 3:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 15:26 Dave Hansen
2009-07-24 0:08 ` KAMEZAWA Hiroyuki
2009-07-24 3:02 ` Li Zefan
2009-07-24 3:08 ` KAMEZAWA Hiroyuki
2009-07-24 3:26 ` Benjamin Blum [this message]
2009-07-24 15:07 ` Paul Menage
2009-07-24 23:38 ` Andrew Morton
2009-08-14 17:56 ` Dan Williams
2009-08-14 19:02 ` Dave Hansen
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=2f86c2480907232026v143aef06t652796b489b7ad2c@mail.gmail.com \
--to=bblum@google.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=mikew@google.com \
--cc=vda.linux@googlemail.com \
--cc=xiyou.wangcong@gmail.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 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®