From: David Miller <davem@davemloft.net>
To: edumazet@google.com
Cc: ycheng@google.com, ncardwell@google.com, fw@strlen.de,
netdev@vger.kernel.org, soheil@google.com, weiwan@google.com,
brakmo@fb.com, lorenzo@google.com, vanj@google.com
Subject: Re: [RFC net-next 0/6] tcp: remove prequeue and header prediction
Date: Mon, 31 Jul 2017 14:38:18 -0700 (PDT) [thread overview]
Message-ID: <20170731.143818.699405961193908260.davem@davemloft.net> (raw)
In-Reply-To: <CANn89i+m4gSTevvMJMt_qOF7Q-ugqLm-jNh+2aKZDSXWR48Ouw@mail.gmail.com>
From: Eric Dumazet <edumazet@google.com>
Date: Mon, 31 Jul 2017 13:22:22 -0700
> On Mon, Jul 31, 2017 at 1:04 PM, Yuchung Cheng <ycheng@google.com> wrote:
>> by the time these devices use 4.12 kernels they are likely powerful
>> enough to make header prediction irrelevant...
>
> Also note that TCP stack complexity has increased a lot, I seriously
> doubt anyone could notice any difference.
>
> On small devices, the major cost is the wakeup of the cpu to process
> one frame before going back to idle...
I agree with Yuchung and Eric on all counts.
prev parent reply other threads:[~2017-07-31 21:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 23:31 [RFC net-next 0/6] tcp: remove prequeue and header prediction Florian Westphal
2017-07-27 23:31 ` [RFC PATCH net-next 1/6] tcp: remove prequeue support Florian Westphal
2017-07-27 23:31 ` [RFC PATCH net-next 2/6] tcp: reindent two spots after prequeue removal Florian Westphal
2017-07-27 23:31 ` [RFC PATCH net-next 3/6] tcp: remove low_latency sysctl Florian Westphal
2017-07-27 23:31 ` [RFC PATCH net-next 4/6] tcp: remove header prediction Florian Westphal
2017-07-27 23:31 ` [RFC PATCH net-next 5/6] tcp: remove CA_ACK_SLOWPATH Florian Westphal
2017-07-27 23:31 ` [RFC PATCH net-next 6/6] tcp: remove unused mib counters Florian Westphal
2017-07-28 19:19 ` [RFC net-next 0/6] tcp: remove prequeue and header prediction Yuchung Cheng
2017-07-29 22:22 ` David Miller
2017-07-30 2:25 ` Neal Cardwell
2017-07-31 20:04 ` Yuchung Cheng
2017-07-31 20:22 ` Eric Dumazet
2017-07-31 21:38 ` 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=20170731.143818.699405961193908260.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brakmo@fb.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=lorenzo@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=soheil@google.com \
--cc=vanj@google.com \
--cc=weiwan@google.com \
--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).