All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: nfs@lists.sourceforge.net
Subject: Different NFSSVC_MAXBLKSIZE for udp and tcp clients?
Date: Tue, 25 Nov 2003 17:34:20 +0000	[thread overview]
Message-ID: <3FC3929C.EFFE5CDF@moving-picture.com> (raw)

Is it possible to force a different maximum [rw]size on the server
depending on whether the client uses udp or tcp?

Currently, when a client NFS mounts a file system without specifying a
[rw]size, it defaults to whatever NFSSVC_MAXBLKSIZE was defined as (at
compile time) on the server. However, this is the same for udp and tcp
clients.

What I would like is to have a smaller default [rw]size for udp clients,
but allow tcp clients to use 32k.

Is this possible?

Thanks

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

             reply	other threads:[~2003-11-25 17:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25 17:34 James Pearson [this message]
2003-11-26  1:08 ` Different NFSSVC_MAXBLKSIZE for udp and tcp clients? 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
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=3FC3929C.EFFE5CDF@moving-picture.com \
    --to=james-p@moving-picture.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.