From: Steve Dickson <SteveD@redhat.com>
To: randy <paries@knology.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: Redhat 9 tcpmounting
Date: Mon, 30 Aug 2004 13:23:18 -0400 [thread overview]
Message-ID: <41336286.7070504@RedHat.com> (raw)
In-Reply-To: <E1C1nil-0004L7-0H@sc8-sf-mx2.sourceforge.net>
randy wrote:
>Does anyone know the option I would have to enable in the config when
>building the kernel?
>
>
CONFIG_NFSD_TCP=y but buyer beware.... FC1 will do this much better
plus its configured in by default....
>Also is there a enough performance gain to warrant recompiling the kernel?
>
>
Well it depends on how clean your networks is. If you're getting a bunch
of retransmits
using UDP, then TCP should smooth things out (since TCP is much better
at dealing
with retransmits that RPC over UDP), but if the traffic is already
pretty smooth, then
performance may decrease a very small amount due to the TCP overhead.....
But the gains of using a smarter transport (i.e. TCP) outweighs the very
small performance hit... imho...
SteveD.
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-08-30 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7E0DB3A126BA9146AC30744E2B7E4245111946@midhouhqxch01.net.smith.com>
2004-08-30 12:53 ` Redhat 9 tcpmounting randy
2004-08-30 17:23 ` Steve Dickson [this message]
2004-08-30 17:38 ` randy
2004-08-29 7:29 server local.flanders not responding, still trying on console randy
2004-08-29 7:34 ` Redhat 9 tcpmounting randy
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=41336286.7070504@RedHat.com \
--to=steved@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=paries@knology.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.