From: Florian Westphal <fw@strlen.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Florian Westphal <fw@strlen.de>,
netdev@vger.kernel.org, Neal Cardwell <ncardwell@google.com>,
Yuchung Cheng <ycheng@google.com>
Subject: Re: [PATCH next resend] tcp: use zero-window when free_space is low
Date: Thu, 13 Feb 2014 16:34:41 +0100 [thread overview]
Message-ID: <20140213153441.GJ25153@breakpoint.cc> (raw)
In-Reply-To: <1392303499.1752.19.camel@edumazet-glaptop2.roam.corp.google.com>
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Do we have one SNMP counter tracking number of time we took the decision
> to send a 0 window ?
No.
> Would you mind waiting we run our packetdrill tests before acknowledging
> this patch, because I suspect this might have some impact ?
Of course not. I am very happy that you folks have these kinds of tests
and are willing to double-check. Take all time you need, there is no
need to haste.
Many Thanks Eric.
Do you think it makes sense to add counters for this?
The caveat is that decision to send 0 window doesn't mean we end
up sending one, since we cannot shrink already offered window.
static u16 tcp_select_window(struct sock *sk)
{
struct tcp_sock *tp = tcp_sk(sk);
u32 cur_win = tcp_receive_window(tp);
u32 new_win = __tcp_select_window(sk);
/* Never shrink the offered window */
if (new_win < cur_win) {
Would you add SNMP counter for '__tcp_select_window() wants 0 window'
or for 'tcp_select_window() does pick 0 window' ?
[ or even different counters for both ? ]
Cheers,
Florian
next prev parent reply other threads:[~2014-02-13 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 11:52 [PATCH next resend] tcp: use zero-window when free_space is low Florian Westphal
2014-02-13 14:58 ` Eric Dumazet
2014-02-13 15:34 ` Florian Westphal [this message]
2014-02-13 16:19 ` Eric Dumazet
2014-02-13 17:18 ` Rick Jones
2014-02-17 19:34 ` David Miller
2014-02-17 20:52 ` Florian Westphal
2014-02-18 17:30 ` Eric Dumazet
2014-02-18 23:12 ` Eric Dumazet
2014-02-19 21:36 ` David Miller
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=20140213153441.GJ25153@breakpoint.cc \
--to=fw@strlen.de \
--cc=eric.dumazet@gmail.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.