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

On Thu, Oct 23, 2008 at 02:40:01PM -0500, Steve French (smfrench@gmail.com) wrote:
> I think we already do the same thing as NFS, they still are turning
> off autotuning on the client right?
> 
> If we could set a "sk_min_sndbuf_size" someday (to e.g. twice the size
> of the cifs write frames ie about 112K)  - would that be enough?


You do not need to set sockt buffers, but instead read data in chunks,
which will automatically make a TCP progress.

-- 
	Evgeniy Polyakov

  reply	other threads:[~2008-10-23 20:59 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 [this message]
2008-10-24  1:18                   ` Steve French
2008-10-24  1:30                     ` Jim Rees
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=20081023205937.GB19462@ioremap.net \
    --to=zbr@ioremap.net \
    --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=rees@umich.edu \
    --cc=sjayaraman@suse.de \
    --cc=smfrench@gmail.com \
    /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.