Re: sendmsg blocking with sendtimeout vs. non-blocking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Oct 23, 2008 at 3:59 PM, Evgeniy Polyakov <zbr@xxxxxxxxxxx> wrote:
> On Thu, Oct 23, 2008 at 02:40:01PM -0500, Steve French (smfrench@xxxxxxxxx) 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.

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)
> The other issue is that at least for NFS, the receive buffer must be big
> enough to hold the biggest possible rpc.  If not, a partial rpc will get
> stuck in the buffer and no progress will be made.
>


-- 
Thanks,

Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux