From: afei@jhu.edu
To: Rik van Riel <riel@nl.linux.org>
Cc: afei@jhu.edu, Chris Vaill <cvaill@cs.columbia.edu>, linux-mm@kvack.org
Subject: Re: Motivation for page replace alg.?
Date: Thu, 09 Dec 1999 16:10:43 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.05.9912091608000.11818-100000@aa.eps.jhu.edu> (raw)
In-Reply-To: <Pine.LNX.4.05.9912092053420.17600-100000@humbolt.nl.linux.org>
If the Linux-MM team would accept it, I am willing to contribute this
document to help to understand Linux memory management. But before that, I
need to clean up the document and make it more readable. I will later on
use Latex to do it (just some copy/paste).
Fei
On Thu, 9 Dec 1999, Rik van Riel wrote:
> On Thu, 9 Dec 1999 afei@jhu.edu wrote:
>
> > Chris, we have done some analysis on this problem. Please check out the
> > online document about linux memory management at:
> > http://aa.eps.jhu.edu/~feiliu/Linux
> >
> > sorry about the readability, it is converted from word. I will work on the
> > layout later, but the content is there.
>
> I know this is a scholl assignment, but
> would it be possible to publish the
> docs on the web, for instance at the Linux-MM
> site?
>
> Rik
> --
> The Internet is not a network of computers. It is a network
> of people. That is its real strength.
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://humbolt.geo.uu.nl/Linux-MM/
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' 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-12-09 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 10:21 Chris Vaill
1999-12-09 19:37 ` afei
1999-12-09 20:16 ` Rik van Riel
1999-12-09 21:10 ` afei [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.GSO.4.05.9912091608000.11818-100000@aa.eps.jhu.edu \
--to=afei@jhu.edu \
--cc=cvaill@cs.columbia.edu \
--cc=linux-mm@kvack.org \
--cc=riel@nl.linux.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