public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: Benjamin Blum <bblum@google.com>,
	containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, menage@google.com,
	akpm@linux-foundation.org
Subject: Re: [PATCH 1/3] Adds a read-only "procs" file similar to "tasks" that shows only unique tgids
Date: Wed, 15 Jul 2009 09:31:56 +0800	[thread overview]
Message-ID: <4A5D318C.5090508@cn.fujitsu.com> (raw)
In-Reply-To: <1247608169.13426.16602.camel@nimitz>

Dave Hansen wrote:
> On Tue, 2009-07-14 at 14:26 -0700, Benjamin Blum wrote:
>> This method looks to be a compromise between Andrew's proposed
>> generalized solution ( http://lkml.org/lkml/2009/7/2/518 ) and the
>> current quick-fix. The problem with it is that it'll require a layer
>> between whoever's using the array and managing the list structs (for
>> the case where we need to chain multiple blocks together), and if
>> we're going to put forth enough effort for that, we may as well go
>> ahead and write up a generalized kernel-wide library to fix this size
>> problem globally.
> 
> This "Andrew" guy seems to know what he's talking about. :)
> 
> We've also got a set of pgarrs (struct page arrays) in the
> checkpoint/restart code that would make use of something generic like
> this.  
> 

The dynamic-page-array thing sounds a right way to go. It's open-coded
in some other places, ring_buffer.c is one among.


  parent reply	other threads:[~2009-07-15  1:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10 23:01 [PATCH v2 0/3] CGroups: cgroup member list enhancement/fix Ben Blum
2009-07-10 23:01 ` [PATCH 1/3] Adds a read-only "procs" file similar to "tasks" that shows only unique tgids Ben Blum
2009-07-13  3:46   ` Li Zefan
2009-07-13 15:25     ` Benjamin Blum
2009-07-14 18:34   ` Dave Hansen
2009-07-14 21:26     ` Benjamin Blum
2009-07-14 21:49       ` Dave Hansen
2009-07-14 22:55         ` Benjamin Blum
2009-07-15  1:31         ` Li Zefan [this message]
2009-07-10 23:02 ` [PATCH 2/3] Ensures correct concurrent opening/reading of pidlists across pid namespaces Ben Blum
2009-07-11 21:59   ` Serge E. Hallyn
2009-07-10 23:02 ` [PATCH 3/3] Quick vmalloc vs kmalloc fix to the case where array size is too large Ben Blum
2009-07-13  3:03   ` Li Zefan
2009-07-13  6:03     ` KAMEZAWA Hiroyuki
2009-07-13 15:27       ` Benjamin Blum
2009-07-13 23:49         ` KAMEZAWA Hiroyuki
2009-07-14  3:50           ` Paul Menage
2009-07-14  3:53             ` KAMEZAWA Hiroyuki
2009-07-14  4:04               ` Paul Menage
2009-07-14  4:25                 ` KAMEZAWA Hiroyuki
2009-07-14 17:26                   ` Benjamin Blum
2009-07-14 17:28                   ` Paul Menage
2009-07-14 17:47                     ` Dave Hansen
2009-07-14 17:50                       ` Paul Menage
2009-07-14 21:30                         ` Benjamin Blum

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=4A5D318C.5090508@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=bblum@google.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.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