linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Jared Hulbert <jaredeh@gmail.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: defrag memory
Date: Thu, 26 May 2005 13:59:18 -0700	[thread overview]
Message-ID: <1117141158.27082.22.camel@localhost> (raw)
In-Reply-To: <6934efce0505261214345a609f@mail.gmail.com>

On Thu, 2005-05-26 at 12:14 -0700, Jared Hulbert wrote:
> Is there a kernel mechanism to force a defrag of memory?

No.

There are a few efforts (external patches) to decrease fragmentation to
allow for more ease in removing memory, or allocating larger physically
contiguous areas, but nothing in mainline or -mm.

Is there a particular reason you're interested?

-- Dave

--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2005-05-26 20:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 19:14 Jared Hulbert
2005-05-26 20:59 ` Dave Hansen [this message]
2005-06-03 20:19   ` Jared Hulbert
2005-06-03 20:40     ` 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=1117141158.27082.22.camel@localhost \
    --to=haveblue@us.ibm.com \
    --cc=jaredeh@gmail.com \
    --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