From: Andrew Morton <akpm@osdl.org>
To: Olof Johansson <olof@austin.ibm.com>
Cc: nathanl@austin.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Increase number of dynamic inodes in procfs (2.6.5)
Date: Tue, 13 Apr 2004 22:19:56 -0700 [thread overview]
Message-ID: <20040413221956.448f7d67.akpm@osdl.org> (raw)
In-Reply-To: <Pine.A41.4.44.0404132332170.80688-100000@forte.austin.ibm.com>
Olof Johansson <olof@austin.ibm.com> wrote:
>
> On Tue, 13 Apr 2004, Andrew Morton wrote:
>
> > > and changes the inode number
> > > allocator to use a growable linked list of bitmaps.
> >
> > This open-codes a simple version of lib/idr.c. Please use lib/idr.c
> > instead. There's an example in fs/super.c
>
> The drawback of using lib/idr.c is the increased memory consumption for
> keeping track of the pointers that are not used. For 100k entries that's
> 800KB lost (64-bit arch).
Which is less that 2% of the space which is used by the 100k inodes.
We've previously discussed allocating the idr pointer array separately, but
the extra cache miss for the users who need it, plus the 2% argument keep
on trumping that. (We could avoid the cache miss with zero-length-array
tricks, actually).
> I've abstracted out Martin Bligh's and Ingo Molnar's scalable bitmap
> allocator that is used by the PID allocator.
Your current requirement does not appear to justify this additional
infrastructure.
next prev parent reply other threads:[~2004-04-14 5:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 19:36 Nathan Lynch
2004-04-14 0:06 ` Andrew Morton
2004-04-14 5:01 ` Olof Johansson
2004-04-14 5:06 ` Olof Johansson
2004-04-14 5:19 ` Andrew Morton [this message]
2004-04-15 2:38 ` Nathan Lynch
2004-04-15 2:51 ` Andrew Morton
2004-04-15 3:13 ` Nathan Lynch
2004-04-15 3:21 ` Andrew Morton
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=20040413221956.448f7d67.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathanl@austin.ibm.com \
--cc=olof@austin.ibm.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®