From: James Pearson <james-p@moving-picture.com>
To: Greg Banks <gnb@melbourne.sgi.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: Different NFSSVC_MAXBLKSIZE for udp and tcp clients?
Date: Wed, 26 Nov 2003 10:43:34 +0000 [thread overview]
Message-ID: <3FC483D6.6753DCA3@moving-picture.com> (raw)
In-Reply-To: 3FC3FD0C.B2DD2183@melbourne.sgi.com
Greg Banks wrote:
>
> James Pearson wrote:
> >
> > Is it possible to force a different maximum [rw]size on the server
> > depending on whether the client uses udp or tcp?
>
> If someone writes the code, e.g. some new export options?
Do you know if this would be possible with 2.4 kernels?
If it is possible, and someone could give me some pointers, I won't mind
giving it a a go ...
James Pearson
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-11-26 10:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 17:34 Different NFSSVC_MAXBLKSIZE for udp and tcp clients? James Pearson
2003-11-26 1:08 ` Greg Banks
2003-11-26 1:40 ` Trond Myklebust
2003-11-26 1:51 ` Greg Banks
2003-11-26 2:00 ` Trond Myklebust
2003-11-26 10:43 ` James Pearson [this message]
2003-11-26 22:15 ` Neil Brown
2003-11-27 0:21 ` Greg Banks
2003-11-27 0:35 ` Neil Brown
2003-11-27 1:33 ` Greg Banks
-- strict thread matches above, loose matches on Subject: below --
2003-11-26 14:20 Lever, Charles
2003-11-27 0:08 ` Greg Banks
2003-11-27 0:53 ` Trond Myklebust
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=3FC483D6.6753DCA3@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=gnb@melbourne.sgi.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.