From: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Benjamin Blum <bblum-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: vda.linux-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org
Subject: Re: [RFCv2][PATCH] flexible array implementation
Date: Wed, 22 Jul 2009 14:51:04 -0700 [thread overview]
Message-ID: <1248299464.24021.334.camel@nimitz> (raw)
In-Reply-To: <2f86c2480907221357j5a09fd9au890f815db3750187-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, 2009-07-22 at 13:57 -0700, Benjamin Blum wrote:
> Does the array automatically grow if you give it more elements than
> you tell it it can have?
The only limits it has or enforces are the structural and architectural
ones dictated by the layout.
> 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.
-- Dave
next prev parent reply other threads:[~2009-07-22 21:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090721220017.60A219D3@kernel>
2009-07-21 22:09 ` [RFCv2][PATCH] flexible array implementation Dave Hansen
[not found] ` <1248214145.13249.5671.camel@nimitz>
2009-07-21 22:35 ` Andrew Morton
2009-07-22 3:25 ` Li Zefan
[not found] ` <4A66868F.4010001@cn.fujitsu.com>
[not found] ` <4A66868F.4010001-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2009-07-22 4:34 ` Dave Hansen
[not found] ` <1248237292.24021.2.camel@nimitz>
2009-07-22 6:14 ` Li Zefan
2009-07-22 7:09 ` Amerigo Wang
[not found] ` <20090722070903.GG6281@cr0.nay.redhat.com>
[not found] ` <20090722070903.GG6281-+dguKlz9DXUf7BdofF/totBPR1lH4CV8@public.gmane.org>
2009-07-22 15:02 ` Dave Hansen
2009-07-22 18:30 ` Matt Helsley
2009-07-22 19:55 ` Mike Waychison
[not found] ` <4A676ECC.1090400-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2009-07-22 22:00 ` Dave Hansen
2009-07-22 20:57 ` Benjamin Blum
[not found] ` <2f86c2480907221357j5a09fd9au890f815db3750187@mail.gmail.com>
[not found] ` <2f86c2480907221357j5a09fd9au890f815db3750187-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-22 21:51 ` Dave Hansen [this message]
2009-07-22 23:20 ` Benjamin Blum
[not found] ` <2f86c2480907221620u6da3a8e3h8273f6a9ee156f86@mail.gmail.com>
[not found] ` <2f86c2480907221620u6da3a8e3h8273f6a9ee156f86-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-23 5:41 ` Dave Hansen
[not found] ` <20090722183018.GE5878@count0.beaverton.ibm.com>
[not found] ` <20090722183018.GE5878-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2009-07-22 22:03 ` Dave Hansen
2009-07-23 2:45 ` H. Peter Anvin
[not found] ` <4A67CEB7.2080505@zytor.com>
[not found] ` <4A67CEB7.2080505-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2009-07-23 14:30 ` Dave Hansen
2009-07-21 22:00 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=1248299464.24021.334.camel@nimitz \
--to=dave-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=bblum-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=vda.linux-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.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