From: Eric Dumazet <eric.dumazet@gmail.com>
To: Krishna Kumar <krkumar2@in.ibm.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] [RFC] tcp: TSQ - do not always throttle.
Date: Tue, 17 Jul 2012 15:10:54 +0200 [thread overview]
Message-ID: <1342530654.2626.563.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120717120358.16611.98190.sendpatchset@localhost.localdomain>
On Tue, 2012-07-17 at 17:33 +0530, Krishna Kumar wrote:
> Do not throttle if sysctl_tcp_limit_output_bytes==0.
>
> Maybe it is better to throttle earlier in the loop, after
> calling tcp_init_tso_segs().
>
I wonder why, and why you put this question in a changelog instead of
outside of it...
Idea was to avoid setting TSQ_THROTTLED if we break out the loop.
About disabling TSQ, my initial intent was to instead use a negative
sysctl_tcp_limit_output_bytes value.
Thats why I have in tcp_transmit_skb() :
skb->destructor = (sysctl_tcp_limit_output_bytes > 0) ?
tcp_wfree : sock_wfree;
So I suggest you change the tcp_write_xmit(() test to a single unsigned
compare :
if (atomic_read(&sk->sk_wmem_alloc) >=
(unsigned) sysctl_tcp_limit_output_bytes) {
Also use :
skb->destructor = (sysctl_tcp_limit_output_bytes >= 0) ?
tcp_wfree : sock_wfree;
and document the 'negative value disables TSQ' in
Documentation/networking/ip-sysctl.txt
next prev parent reply other threads:[~2012-07-17 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 12:03 [PATCH] [RFC] tcp: TSQ - do not always throttle Krishna Kumar
2012-07-17 13:10 ` Eric Dumazet [this message]
2012-07-17 14:08 ` Krishna Kumar2
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=1342530654.2626.563.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=krkumar2@in.ibm.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