netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jbaron@akamai.com
Cc: edumazet@google.com, netdev@vger.kernel.org,
	ncardwell@google.com, ycheng@google.com, ycao009@ucr.edu
Subject: Re: [PATCH net] tcp: enable per-socket rate limiting of all 'challenge acks'
Date: Fri, 15 Jul 2016 14:18:42 -0700 (PDT)	[thread overview]
Message-ID: <20160715.141842.54072741247152503.davem@davemloft.net> (raw)
In-Reply-To: <1468510720-322-1-git-send-email-jbaron@akamai.com>

From: Jason Baron <jbaron@akamai.com>
Date: Thu, 14 Jul 2016 11:38:40 -0400

> From: Jason Baron <jbaron@akamai.com>
> 
> The per-socket rate limit for 'challenge acks' was introduced in the
> context of limiting ack loops:
> 
> commit f2b2c582e824 ("tcp: mitigate ACK loops for connections as tcp_sock")
> 
> And I think it can be extended to rate limit all 'challenge acks' on a
> per-socket basis.
> 
> Since we have the global tcp_challenge_ack_limit, this patch allows for
> tcp_challenge_ack_limit to be set to a large value and effectively rely on
> the per-socket limit, or set tcp_challenge_ack_limit to a lower value and
> still prevents a single connections from consuming the entire challenge ack
> quota.
> 
> It further moves in the direction of eliminating the global limit at some
> point, as Eric Dumazet has suggested. This a follow-up to:
> Subject: tcp: make challenge acks less predictable
> 
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: Neal Cardwell <ncardwell@google.com>
> Cc: Yuchung Cheng <ycheng@google.com>
> Cc: Yue Cao <ycao009@ucr.edu>
> Signed-off-by: Jason Baron <jbaron@akamai.com>

Applied, thanks.

      parent reply	other threads:[~2016-07-15 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 15:38 [PATCH net] tcp: enable per-socket rate limiting of all 'challenge acks' Jason Baron
2016-07-15 13:39 ` Neal Cardwell
2016-07-15 21:18 ` David Miller [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=20160715.141842.54072741247152503.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jbaron@akamai.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=ycao009@ucr.edu \
    --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 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).