From: Eric Dumazet <eric.dumazet@gmail.com>
To: Yuchung Cheng <ycheng@google.com>, Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Jean-Louis Dupond <jean-louis@dupond.be>,
Neal Cardwell <ncardwell@google.com>
Subject: Re: [PATCH net-next 3/3] tcp: implement head drops in backlog queue
Date: Wed, 21 Nov 2018 14:47:44 -0800 [thread overview]
Message-ID: <f86128c2-1109-a397-3a70-098556c21cea@gmail.com> (raw)
In-Reply-To: <CAK6E8=d1CxqkYy+Ad9Vw4NpP_6UKir5Rik=EuN=zGD8o-4USWQ@mail.gmail.com>
On 11/21/2018 02:40 PM, Yuchung Cheng wrote:
> On Wed, Nov 21, 2018 at 9:52 AM, Eric Dumazet <edumazet@google.com> wrote:
>> Under high stress, and if GRO or coalescing does not help,
>> we better make room in backlog queue to be able to keep latest
>> packet coming.
>>
>> This generally helps fast recovery, given that we often receive
>> packets in order.
>
> I like the benefit of fast recovery but I am a bit leery about head
> drop causing HoLB on large read, while tail drops can be repaired by
> RACK and TLP already. Hmm -
This is very different pattern here.
We have a train of packets coming, the last packet is not a TLP probe...
Consider this train coming from an old stack without burst control nor pacing.
This patch guarantees last packet will be processed, and either :
1) We are a receiver, we will send a SACK. Sender will typically start recovery
2) We are a sender, we will process the most recent ACK sent by the receiver.
next prev parent reply other threads:[~2018-11-22 9:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 17:52 [PATCH net-next 0/3] tcp: take a bit more care of backlog stress Eric Dumazet
2018-11-21 17:52 ` [PATCH net-next 1/3] tcp: remove hdrlen argument from tcp_queue_rcv() Eric Dumazet
2018-11-21 22:41 ` Yuchung Cheng
2018-11-21 17:52 ` [PATCH net-next 2/3] tcp: implement coalescing on backlog queue Eric Dumazet
2018-11-21 22:31 ` Yuchung Cheng
2018-11-21 22:40 ` Eric Dumazet
2018-11-22 16:34 ` Yuchung Cheng
2018-11-22 18:01 ` Neal Cardwell
2018-11-22 18:16 ` Eric Dumazet
2018-11-22 18:21 ` Eric Dumazet
2018-11-21 17:52 ` [PATCH net-next 3/3] tcp: implement head drops in " Eric Dumazet
2018-11-21 22:40 ` Yuchung Cheng
2018-11-21 22:47 ` Eric Dumazet [this message]
2018-11-21 23:46 ` Yuchung Cheng
2018-11-21 23:52 ` Eric Dumazet
2018-11-22 0:18 ` Eric Dumazet
2018-11-22 0:54 ` Yuchung Cheng
2018-11-22 1:01 ` Eric Dumazet
2018-11-23 19:25 ` [PATCH net-next 0/3] tcp: take a bit more care of backlog stress David Miller
2018-11-23 19:27 ` Eric Dumazet
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=f86128c2-1109-a397-3a70-098556c21cea@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jean-louis@dupond.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox