All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: nfs@lists.sourceforge.net
Subject: Re: NFS server not responding
Date: Thu, 04 Dec 2003 12:37:29 -0500	[thread overview]
Message-ID: <3FCF70D9.1010808@RedHat.com> (raw)
In-Reply-To: <shsptfch1om.fsf@charged.uio.no>

Trond Myklebust wrote:

>Now it may be that the Fedora kernel has some other crap in it that is
>screwing up interrupts & other such things (NAPI perhaps?). Has
>anybody that is seeing these problems made a comparison with an
>equivalent stock Marcelo kernel?
>  
>
For the recored here is the "crap" that's in FC1 and not in the stock 
kernel:

 From Trond's Tree:
    linux-2.4.x-rdplus.dif
    linux-2.4.x-cto.dif
    linux-2.4.x-pathconf.dif

 From -ac1 tree:
    kmap() calls changed to kmap_atomic() calls
   
Patches posted to this list:
    linux-2.4.21-nfs-accesscache.patch - reduces the number of otw 
ACCESS calls
    linux-2.4.20-nfs-ia64-EIO.patch    - increase RPC_RTO_MIN to HZ/30

And here are the patches that are in the stock kernel
and not in FC1 (yet)...

# 03/10/11  trond.myklebust@fys.uio.no  1.1148.17.6
# Make the client act correctly if the RPC server's asserts
# that it does not support a given program, version or
# procedure call.

# 03/10/11  trond.myklebust@fys.uio.no  1.1148.17.1
# Fix a deadlock in the NFS asynchronous write code.

SteveD.




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2003-12-04 17:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 12:00 NFS server not responding Douglas Furlong
2003-11-27 16:30 ` Trond Myklebust
2003-11-27 19:07   ` Douglas Furlong
2003-11-27 20:02     ` Trond Myklebust
2003-11-28  8:46 ` Juergen Sauer
2003-11-28  9:37   ` Douglas Furlong
2003-11-28 10:11     ` Juergen Sauer
2003-11-28 10:48       ` Douglas Furlong
2003-11-28 12:28         ` Bogdan Costescu
2003-11-28 16:56           ` Trond Myklebust
2003-11-28 18:43             ` Bogdan Costescu
2003-12-02 14:37             ` Douglas Furlong
2003-12-02 15:37               ` Trond Myklebust
2003-12-04 17:17                 ` Steve Dickson
2003-12-04 17:37             ` Steve Dickson [this message]
2003-12-04 18:39               ` Trond Myklebust
2003-12-04 19:11                 ` Steve Dickson
2003-12-04 20:55                   ` seth vidal
2003-12-04 21:24                     ` Steve Dickson
2003-12-05  2:53                       ` Kyle Rose
2003-12-09 19:47                         ` Steve Dickson
2003-12-09 20:09                           ` Kyle Rose
2003-12-05 15:50                 ` Bogdan Costescu
2003-11-30 20:01           ` seth vidal
2003-12-01 10:58             ` Bogdan Costescu
2003-11-28 12:36       ` Bogdan Costescu
  -- strict thread matches above, loose matches on Subject: below --
2004-07-30 17:09 nfs " Pavel Bartusek
2009-05-16  0:57 nfs: " Jerome Walters

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=3FCF70D9.1010808@RedHat.com \
    --to=steved@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.