From: Eric Dumazet <edumazet@google.com>
To: Yuchung Cheng <ycheng@google.com>
Cc: Neal Cardwell <ncardwell@google.com>,
Florian Westphal <fw@strlen.de>, Netdev <netdev@vger.kernel.org>,
Soheil Hassas Yeganeh <soheil@google.com>,
Wei Wang <weiwan@google.com>, Lawrence Brakmo <brakmo@fb.com>,
David Miller <davem@davemloft.net>,
Lorenzo Colitti <lorenzo@google.com>,
Van Jacobson <vanj@google.com>
Subject: Re: [RFC net-next 0/6] tcp: remove prequeue and header prediction
Date: Mon, 31 Jul 2017 13:22:22 -0700 [thread overview]
Message-ID: <CANn89i+m4gSTevvMJMt_qOF7Q-ugqLm-jNh+2aKZDSXWR48Ouw@mail.gmail.com> (raw)
In-Reply-To: <CAK6E8=dyuurH4iT5qf0U=JgOEr3X=mDGtG69-KKz5uj6nFYvwQ@mail.gmail.com>
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...
next prev parent reply other threads:[~2017-07-31 20:22 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 [this message]
2017-07-31 21:38 ` 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=CANn89i+m4gSTevvMJMt_qOF7Q-ugqLm-jNh+2aKZDSXWR48Ouw@mail.gmail.com \
--to=edumazet@google.com \
--cc=brakmo@fb.com \
--cc=davem@davemloft.net \
--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).