From: Christoph Lameter <clameter@engr.sgi.com>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: linux-mm@kvack.org
Subject: Re: Possible cure for memory fragmentation.
Date: Thu, 22 Dec 2005 09:14:03 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.62.0512220908120.7717@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <43AAC5EA.3090800@superbug.demon.co.uk>
On Thu, 22 Dec 2005, James Courtier-Dutton wrote:
> The driver does not call kremalloc with a different size. It calls it with the
> SAME size. Then if the kernel thinks it would benefit from moving the
Umm. When would the kernel do something like that?
Also give it different name. realloc has pretty well established
semantics.
> If the kernel does not wish to move it, kremalloc returns without having done
> anything.
What this all comes down to is to guarantee that only a known number of
references exist to the data element when you move it. For kremalloc these
references must be known and all the pointers to the data element must be
updated if the data is moved. The basic problem is not solved.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-12-22 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 11:46 James Courtier-Dutton
2005-12-21 19:04 ` Christoph Lameter
2005-12-22 15:27 ` James Courtier-Dutton
2005-12-22 17:14 ` Christoph Lameter [this message]
2005-12-22 17:41 ` James Courtier-Dutton
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.4.62.0512220908120.7717@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=James@superbug.demon.co.uk \
--cc=linux-mm@kvack.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