linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: linux-mm@kvack.org
Subject: Memory problems
Date: Fri, 24 Aug 2007 13:36:20 +0100	[thread overview]
Message-ID: <46CED0C4.70107@superbug.co.uk> (raw)

Hi,

Is there anywhere that documents the current problems that Linux is 
having with memory management.
Are there any "big" problems still outstanding, or is it just a matter 
of fixing edge cases now?
The last time I looked into this, people were having memory pressure 
problems relating to network attached swap space. I believe those 
problems are fixed now and I was able to help there.

Kind Regards

James


--
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>

             reply	other threads:[~2007-08-24 12:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 12:36 James Courtier-Dutton [this message]
     [not found] <Pine.LNX.4.04.9905021624570.18784-100000@ps.cus.umist.ac.uk>
     [not found] ` <Pine.LNX.4.03.9905031237130.219-100000@mirkwood.dummy.home>
1999-05-04  6:09   ` Ralf Baechle

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=46CED0C4.70107@superbug.co.uk \
    --to=james@superbug.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