All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Rees <rees@umich.edu>
To: Steve French <smfrench@gmail.com>
Cc: Evgeniy Polyakov <zbr@ioremap.net>,
	Jeff Layton <jlayton@redhat.com>,
	Shirish Pargaonkar <shirishpargaonkar@gmail.com>,
	Suresh Jayaraman <sjayaraman@suse.de>,
	nhorman@redhat.com,
	"linux-cifs-client@lists.samba.org"
	<linux-cifs-client@lists.samba.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Frank S Filz <ffilz@us.ibm.com>
Subject: Re: sendmsg blocking with sendtimeout vs. non-blocking
Date: Thu, 23 Oct 2008 21:30:32 -0400	[thread overview]
Message-ID: <20081024013032.GA32749@citi.umich.edu> (raw)
In-Reply-To: <524f69650810231818m5d31d4acp7f1e7a88aae54641@mail.gmail.com>

Steve French wrote:

  If that is the case (ie that cifs and nfs never need to set these over
  tcp - I am still having trouble reconciling that with the NFS guys'
  comments that they must set rcvbuf (and Jim's comment below)

If you have an application that wants to read a big chunk of data from a
socket, and won't remove any of that data from the socket until the entire
chunk has arrived, then the application must set the receive socket buffer
size big enough to hold the entire chunk.  Otherwise the application will
stall.

As far as I can tell, the corresponding situation does not hold for send
buffers, because the tcp layer will grow the send buffer to be big enough to
hold whatever the application wants to send.  But I don't know if that's
always true, or if there is some limit, so to be safe our NFS patch
continues to set both the receive and send buffer sizes.

  reply	other threads:[~2008-10-24  1:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <524f69650810221414n52e236d9rfc6f231d1db75405@mail.gmail.com>
     [not found] ` <20081023091325.0ad059c6@barsoom.rdu.redhat.com>
     [not found]   ` <524f69650810230754m20b815b5n256e82ef1d5dd4f0@mail.gmail.com>
     [not found]     ` <4a4634330810230926m9285a3etf6340e3de53c576@mail.gmail.com>
2008-10-23 16:42       ` sendmsg blocking with sendtimeout vs. non-blocking Steve French
2008-10-23 17:40         ` Steve French
2008-10-23 17:46           ` Evgeniy Polyakov
2008-10-23 18:00         ` Jeff Layton
2008-10-23 19:19           ` Steve French
2008-10-23 19:35             ` Jeff Layton
2008-10-23 19:40               ` Steve French
2008-10-23 20:59                 ` Evgeniy Polyakov
2008-10-24  1:18                   ` Steve French
2008-10-24  1:30                     ` Jim Rees [this message]
2008-10-24  1:48                       ` Jeff Layton
2008-10-24 12:53                       ` Neil Horman
2008-10-24 13:59                         ` Jim Rees
2008-10-24 15:20                           ` Evgeniy Polyakov
2008-10-24 15:36                             ` Jim Rees
2008-10-24 15:29                           ` Neil Horman
2008-10-24 14:23                         ` Steve French
2008-10-24 15:02                           ` Shirish Pargaonkar
2008-10-24 16:18                             ` Steve French
2008-10-24  1:52                     ` Trond Myklebust
2008-10-24  2:06                       ` Steve French
2008-10-24  4:43                         ` Trond Myklebust
2008-10-23 20:02               ` Jim Rees
2008-10-23 20:18                 ` Neil Horman

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=20081024013032.GA32749@citi.umich.edu \
    --to=rees@umich.edu \
    --cc=ffilz@us.ibm.com \
    --cc=jlayton@redhat.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=nhorman@redhat.com \
    --cc=shirishpargaonkar@gmail.com \
    --cc=sjayaraman@suse.de \
    --cc=smfrench@gmail.com \
    --cc=zbr@ioremap.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.