public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Benjamin Blum <bblum@google.com>
Cc: vda.linux@googlemail.com, containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, menage@google.com,
	akpm@linux-foundation.org
Subject: Re: [RFCv2][PATCH] flexible array implementation
Date: Wed, 22 Jul 2009 22:41:37 -0700	[thread overview]
Message-ID: <1248327697.24021.661.camel@nimitz> (raw)
In-Reply-To: <2f86c2480907221620u6da3a8e3h8273f6a9ee156f86@mail.gmail.com>

On Wed, 2009-07-22 at 16:20 -0700, Benjamin Blum wrote:
> 
> >> How about a resize() function that can be
> >> used to either grow or shrink the array?
> >
> > I think growing is out of the question.  It has a fixed maximum size
> > already.  As for shrinking, there's probably a use case for when
> > something is large, then shrinks back down.  But, I think I'd want to
> > see a user for it, otherwise I'm just guessing at it too much.
> 
> Check out the reallocate logic in pidlist_uniq from my patch (the
> series you linked).

To me, it seems like you should just replace the cgroup_pidlist->list
with a 'struct flex_array *'.  It sounds like you're concerned that a
large cgroup_pidlist that was later shrunk would take up too much space.

That's a valid concern and it would be quite possible to make a
flex_array_clean() or truncate() or something similar.  Such a function,
given an index, could clean out the array at all points past the given
index.  Kinda the opposite of prealloc().

At the same time, you could get the same effect by allocating a new flex
array and doing copies like you are now with the normal arrays.  

-- Dave


  reply	other threads:[~2009-07-23  5:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 22:00 [RFCv2][PATCH] flexible array implementation Dave Hansen
2009-07-21 22:09 ` Dave Hansen
2009-07-21 22:35   ` Andrew Morton
2009-07-22  3:25 ` Li Zefan
2009-07-22  4:34   ` Dave Hansen
2009-07-22  6:14     ` Li Zefan
2009-07-22  7:09 ` Amerigo Wang
2009-07-22 15:02   ` Dave Hansen
2009-07-22 18:30 ` Matt Helsley
2009-07-22 22:03   ` Dave Hansen
2009-07-22 19:55 ` Mike Waychison
2009-07-22 22:00   ` Dave Hansen
2009-07-22 20:57 ` Benjamin Blum
2009-07-22 21:51   ` Dave Hansen
2009-07-22 23:20     ` Benjamin Blum
2009-07-23  5:41       ` Dave Hansen [this message]
2009-07-23  2:45 ` H. Peter Anvin
2009-07-23 14:30   ` 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=1248327697.24021.661.camel@nimitz \
    --to=dave@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bblum@google.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=vda.linux@googlemail.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