From: "Shirish Pargaonkar" <shirishpargaonkar@gmail.com>
To: "Jeremy Jackson" <jerj@coplanar.net>
Cc: "Sridhar Samudrala" <sri@us.ibm.com>,
linux-net@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: autotuning of send buffer size of a socket
Date: Wed, 14 May 2008 13:37:38 -0500 [thread overview]
Message-ID: <4a4634330805141137y25c54b1t19992e777c00d8b5@mail.gmail.com> (raw)
In-Reply-To: <1210789577.6956.9.camel@ragnarok>
On 5/14/08, Jeremy Jackson <jerj@coplanar.net> wrote:
> Sorry if this has been covered already, but doesn't Samba set the write
> buffer size, thereby disabling autotuning?
>
> --
> Jeremy Jackson
> Coplanar Networks
> (519)489-4903
> http://www.coplanar.net
> jerj@coplanar.net
>
>
Jeremy,
I would like auto-tuning to happen on the machine running cifs/samba client.
That is where the errors are logged. The auto-tune happens on the client side,
just not good enough to ward off the delays (and subsequent errors logged
by cifs client and reconnects initated by cifs client to samba server
running on other
machine.) for reasons.
Regards,
Shirish
next prev parent reply other threads:[~2008-05-14 18:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4a4634330805121200m739e67bdife66c3ad81af1ceb@mail.gmail.com>
2008-05-13 0:47 ` autotuning of send buffer size of a socket Sridhar Samudrala
2008-05-13 0:51 ` David Miller
2008-05-13 13:54 ` Shirish Pargaonkar
2008-05-13 23:48 ` Sridhar Samudrala
2008-05-14 14:22 ` Shirish Pargaonkar
2008-05-14 18:11 ` Shirish Pargaonkar
2008-05-14 18:26 ` Jeremy Jackson
2008-05-14 18:37 ` Shirish Pargaonkar [this message]
2008-05-14 20:23 ` Shirish Pargaonkar
2008-05-15 4:18 ` Shirish Pargaonkar
2008-05-15 15:00 ` Shirish Pargaonkar
2008-05-15 17:40 ` Sridhar Samudrala
2008-05-15 18:03 ` Shirish Pargaonkar
2008-05-15 18:49 ` Shirish Pargaonkar
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=4a4634330805141137y25c54b1t19992e777c00d8b5@mail.gmail.com \
--to=shirishpargaonkar@gmail.com \
--cc=jerj@coplanar.net \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.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 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).