linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alok Mooley <rangdi@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Active Memory Defragmentation : Need?
Date: Sat, 2 Aug 2003 13:38:15 -0700 (PDT)	[thread overview]
Message-ID: <20030802203815.95358.qmail@web9702.mail.yahoo.com> (raw)

Why is Active Memory Defragmentation needed? 
(Reference : Paper by Daniel Phillips , titled 
"Patch:My research agenda for 2.7").
 
      Is there any case or example of the Linux memory
allocator (buddy allocator) failing due to memory
fragmentation? If yes,what sorts of programs or
applications cause this failure?
      Could anyone kindly supply me with statistical
data & arguments to justify the need for Active Memory Defragmentation?

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

             reply	other threads:[~2003-08-02 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-02 20:38 Alok Mooley [this message]
2003-08-02 20:39 Active Memory Defragmentation : Need? Alok Mooley

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=20030802203815.95358.qmail@web9702.mail.yahoo.com \
    --to=rangdi@yahoo.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).