From: Rick Jones <rick.jones2@hp.com>
To: Jack Zhang <jack.zhang2011@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: can TCP socket send buffer be over used?
Date: Tue, 03 Aug 2010 18:17:46 -0700 [thread overview]
Message-ID: <4C58BFBA.8010503@hp.com> (raw)
In-Reply-To: <AANLkTikqTHNmTQL2-QSJZmJ=18CfdZGo41zUE6mKO_PS@mail.gmail.com>
Jack Zhang wrote:
> Hi Rick,
>
> Thanks for your reply.
>
> Do you maybe know which part of the source code implements the details
> about how much send buffer can actually be used for the data payload?
Specifically no. I've not had to go looking for it.
happy benchmarking,
rick jones
next prev parent reply other threads:[~2010-08-04 1:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 0:22 can TCP socket send buffer be over used? Jack Zhang
2010-08-04 0:30 ` Rick Jones
2010-08-04 0:48 ` Jack Zhang
2010-08-04 1:17 ` Rick Jones [this message]
2010-08-04 7:20 ` Bill Fink
2010-08-04 8:00 ` Jack Zhang
2010-08-04 9:07 ` Bill Fink
2010-08-04 7:33 ` Mikael Abrahamsson
2010-08-04 8:03 ` Jack Zhang
2010-08-04 8:21 ` Mikael Abrahamsson
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=4C58BFBA.8010503@hp.com \
--to=rick.jones2@hp.com \
--cc=jack.zhang2011@gmail.com \
--cc=netdev@vger.kernel.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).