linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 must-fix list, v2
Date: 13 May 2003 13:36:14 +0200	[thread overview]
Message-ID: <shswugvjcy9.fsf@charged.uio.no> (raw)
In-Reply-To: <20030512155511.21fb1652.akpm@digeo.com>

>>>>> " " == Andrew Morton <akpm@digeo.com> writes:

     > - NFS client gets an OOM deadlock.
     > - Some fixes exist in -mm.  Seem to mostly work.
     > - NFS client runs very slowly consuming 100% CPU under heavy
     >   writeout.
     > - Unsubtle fix exists in -mm.  (Looks like it's fixed anyway).

<snip>

     > - davej: NFS seems to have a really bad time for some people.  (Including
     >   myself on one testbox).  The common factor seems to be a high
     >   spec client torturing an underpowered NFS server with lots of
     >   IO.  (fsx/fsstress etc show this up).  Lots of "NFS server
     >   cheating" messages get dumped, and a whole lot of bogus
     >   packets start appearing.  They look severely corrupted, (they
     >   even crashed ethereal once 8-)

Could people please test these items out again using the latest
Bitkeeper release? I believe I've addressed all these issues with the
patches that have gone to Linus in the last 2-3 weeks.

Cheers,
  Trond

  parent reply	other threads:[~2003-05-13 11:23 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 22:54 2.6 must-fix list, v2 Andrew Morton
2003-05-12 22:55 ` Andrew Morton
2003-05-13  4:05   ` viro
2003-05-13  5:00     ` Greg KH
2003-05-13 11:36   ` Trond Myklebust [this message]
2003-05-13 13:57     ` Dave Jones
2003-05-13 15:16       ` Trond Myklebust
2003-05-13 15:22         ` Dave Jones
2003-05-13 15:32           ` Trond Myklebust
2003-05-13 15:47             ` Dave Jones
2003-05-13 16:02               ` Trond Myklebust
2003-05-13 16:09                 ` Dave Jones
2003-05-13 16:27                   ` Trond Myklebust
2003-05-13 16:45                     ` Dave McCracken
2003-05-13 16:53                       ` Trond Myklebust
2003-05-13 22:50                         ` Andrew Morton
2003-05-13 17:38                 ` Dave Jones
2003-05-13 17:59                   ` Trond Myklebust
2003-05-13 15:59     ` Daniel Jacobowitz
2003-05-13 16:11       ` Trond Myklebust
2003-05-13 18:09         ` Daniel Jacobowitz
2003-05-13 20:15         ` Chris Friesen
2003-05-13 20:25           ` Trond Myklebust
2003-05-13 13:57   ` Alan Cox
2003-05-13 15:00     ` Jeff Garzik
2003-05-13 15:12       ` Jens Axboe
2003-05-13 15:38     ` Christoph Hellwig
2003-05-13 15:50       ` Jeff Garzik
2003-05-13 16:59         ` Sam Ravnborg
2003-05-13 20:07           ` Geert Uytterhoeven
2003-05-13 20:12             ` Sam Ravnborg
2003-05-13 19:51       ` Geert Uytterhoeven
2003-05-13 20:17       ` Andrew Morton
2003-05-13 22:25         ` Dave Jones
2003-05-13 22:52           ` William Lee Irwin III
2003-05-13 23:43           ` Russell King
2003-05-14  8:09             ` Geert Uytterhoeven
     [not found]         ` <mailman.1052866140.9783.linux-kernel2news@redhat.com>
2003-05-14  2:32           ` Pete Zaitcev
2003-05-14 16:21         ` Tom Rini
2003-05-17  8:58       ` Pavel Machek
2003-05-13 15:47     ` Trond Myklebust
2003-05-13 15:06       ` Alan Cox
2003-05-13 16:20         ` Trond Myklebust
2003-05-13 17:52       ` Miquel van Smoorenburg
2003-05-13 18:11         ` Trond Myklebust
2003-05-17  8:56     ` Pavel Machek
2003-05-13  0:22 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 18:21 Perez-Gonzalez, Inaky
2003-05-14  2:05 Perez-Gonzalez, Inaky
2003-05-14  2:43 ` Zwane Mwaikambo
2003-05-14 12:05   ` Shaheed R. Haque
2003-05-13 20:04 Chuck Ebbert
2003-05-13 17:12 James Bottomley
2003-05-13 18:11 ` Mike Anderson
2003-05-13 18:18   ` James Bottomley
2003-05-13 19:14     ` Mike Anderson
     [not found] <20030512155417.67a9fdec.akpm@digeo.com.suse.lists.linux.kernel>
     [not found] ` <20030512155511.21fb1652.akpm@digeo.com.suse.lists.linux.kernel>
2003-05-13  6:00   ` Andi Kleen
2003-05-13  1:57 Chuck Ebbert
2003-04-12 11:20 Processor sets (pset) for linux kernel 2.5/2.6? Shaheed R. Haque
2003-04-12 19:56 ` Shaheed R. Haque
2003-04-12 20:02   ` Robert Love
2003-04-13  8:30     ` Shaheed R. Haque
2003-04-13 14:28       ` Robert Love
2003-05-13 11:49         ` 2.6 must-fix list, v2 Shaheed R. Haque
2003-05-13 20:02           ` Andrew Morton
2003-05-13 22:46             ` Shaheed R. Haque
2003-05-14  2:42               ` Steven Cole
2003-05-14 11:49                 ` Shaheed R. Haque
2003-05-14 13:08                   ` Steven Cole
2003-05-13 22:49             ` Shaheed R. Haque
2003-05-14 11:02               ` Felipe Alfaro Solana
2003-05-14 15:59                 ` Robert Love
2003-05-14 16:04                   ` Robert Love
2003-05-14 21:01                   ` shaheed
2003-05-14 21:15                     ` Robert Love
2003-05-15  9:19                       ` Shaheed R. Haque
2003-05-15 15:32                         ` Robert Love
2003-05-15 20:07                           ` shaheed
2003-05-15 20:20                             ` Robert Love
2003-05-15 20:24                             ` Robert Love
2003-05-15 21:30                               ` shaheed

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=shswugvjcy9.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=akpm@digeo.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).