From: Andrew Morton <akpm@digeo.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.60-mm2
Date: Fri, 14 Feb 2003 02:22:20 -0800 [thread overview]
Message-ID: <20030214022220.30d0ed69.akpm@digeo.com> (raw)
In-Reply-To: <20030214101356.GA17155@codemonkey.org.uk>
Dave Jones <davej@codemonkey.org.uk> wrote:
>
> On Fri, Feb 14, 2003 at 01:58:02AM -0800, Andrew Morton wrote:
>
> > > I'm puzzled that you've had NFS stable enough to test these.
> > This was just writing out a single 400 megabyte file with `dd'. I didn't try
> > anything fancier.
>
> ok. Can you hold off pushing NFS bits to Linus until this gets
> pinned down ? I really don't want to introduce any more variables
> to this, especially when its so hard to pin down to an exact
> replication scenario.
I wouldn't push any NFS bits. It has a breathing maintainer ;)
I've been mainly looking at the OOM problems, which need MM help. Got
distracted.
--
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>
next prev parent reply other threads:[~2003-02-14 10:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 9:31 2.5.60-mm2 Andrew Morton
2003-02-14 9:38 ` 2.5.60-mm2 Dave Jones
2003-02-14 9:58 ` 2.5.60-mm2 Andrew Morton
2003-02-14 10:13 ` 2.5.60-mm2 Dave Jones
2003-02-14 10:22 ` Andrew Morton [this message]
2003-02-14 10:10 ` 2.5.60-mm2 Thomas Schlichter
2003-02-17 1:59 ` 2.5.60-mm2 Bill Davidsen
2003-02-17 12:08 ` 2.5.60-mm2 Bill Davidsen
2003-02-17 12:35 ` 2.5.60-mm2 Thomas Schlichter
2003-02-17 18:32 ` 2.5.60-mm2 Bill Davidsen
2003-02-14 20:59 ` compile fail: 2.5.60-mm2 Core
2003-02-14 22:06 ` Andrew Morton
2003-02-15 20:27 ` 2.5.60-mm2 Arador
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=20030214022220.30d0ed69.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--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