From: Steve French <smfltc@us.ibm.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, samba-technical@lists.samba.org,
linux-cifs-client@lists.samba.org
Subject: Re: slow tcp acks on loopback device
Date: 22 Jul 2005 16:42:40 -0500 [thread overview]
Message-ID: <1122068559.29257.32.camel@stevef95.austin.ibm.com> (raw)
In-Reply-To: <20050722.130816.91445335.davem@davemloft.net>
> TCP_NODELAY does not control ACK generation, instead it modifies
> the Nagle algorithm behavior when sending data packets.
Looks like RHEL4 had an odd default smb.conf on the server side - the
RedHat smb.conf seems to set SO_RCVBUF and SO_SNDBUF to 8K (reducing
them from their default). This seems very odd since common TCP frame
sizes for this protocol (SMB/CIFS) will be just over 16K (the negotiated
SMB buffer size) as well as even large frames, 60K, for large read/write
requests which Windows sends. Removing the SO_SNDBUF, SO_RCVBUF options
(as in the smb.conf for other distros), increased performance a lot.
The Samba Howto recommends against setting them so small as well.
The alternative solution configuring the client end - altering ack
behavior to allow the client to do quick(er) acks probably would have
helped too, but of course has sideeffects (more acks) and it was not
obvious to me how to do that safely from a kernel vfs module.
prev parent reply other threads:[~2005-07-22 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1122062219.29258.12.camel@stevef95.austin.ibm.com>
2005-07-22 20:08 ` slow tcp acks on loopback device David S. Miller
2005-07-22 21:42 ` Steve French [this message]
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=1122068559.29257.32.camel@stevef95.austin.ibm.com \
--to=smfltc@us.ibm.com \
--cc=davem@davemloft.net \
--cc=linux-cifs-client@lists.samba.org \
--cc=netdev@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).