From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: Paul Hamshere <ph@clara.net>
Cc: Linux-MM@kvack.org
Subject: Re: Fwd: Inoffensive bug in mm/page_alloc.c
Date: Fri, 29 Jan 1999 20:52:51 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.95.990129204839.24246C-100000@kanga.kvack.org> (raw)
In-Reply-To: <990127235552.n0002181.ph@mail.clara.net>
Hello Paul,
> Is this of any interest here?
Yep!
> Paul
> ------------------------------
> Hi
> I was trawling through the mm sources to try and understand how linux tracks the
> use of pages of memory, how kmalloc and vmalloc work, and I think there is a bug
> in the kernel (2.0) - it doesn't affect anything, only waste a tiny amount of
> memory....does anyone else think it looks wrong?
> The problem is in free_area_init where it allocates the bitmaps - I think they
> are twice the size they need to be.
If you search the mailing list archives from either a year, maybe two ago,
someone brought forth the same concern, but Linus rejected the patch on
the basis that it wasn't trivially proven correct for *all* sizes of
memory. The amount of memory involved is insignificant, and I'd speculate
that we'll see a page allocator in 2.3 at which point that loss can
disappear.
-ben (cleaning out the inbox)
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
prev parent reply other threads:[~1999-01-30 1:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <990119214302.n0001113.ph@mail.clara.net>
1999-01-27 23:55 ` Fwd: Inoffensive bug in mm/page_alloc.c Paul Hamshere
1999-01-30 1:52 ` Benjamin C.R. LaHaise [this message]
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=Pine.LNX.3.95.990129204839.24246C-100000@kanga.kvack.org \
--to=blah@kvack.org \
--cc=Linux-MM@kvack.org \
--cc=ph@clara.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.