From: Matthias Tafelmeier <matthias.tafelmeier@gmx.net>
To: Dave Taht <dave.taht@gmail.com>,
bloat <bloat@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Bloat] Van Jacobson's slides on timing wheels at netdevconf
Date: Sat, 21 Jul 2018 15:19:16 +0200 [thread overview]
Message-ID: <9393eca9-3ac4-46cf-7737-89d1797db975@gmx.net> (raw)
In-Reply-To: <CAA93jw7fzv+pe2CiD6YOZ_n=7zH2XjFW=HaFypbm=B-1OLraXw@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 564 bytes --]
> B) that NIC support seems
> needed. I can think of a lot of things I'd like to have in a NIC
> (which certainly include default timestamping on rx and multiple kinds
> of X-tuple hash) - but hadn't thought about replacing queues entirely!
Still fond of the notion of RX|TX sk buffers wandering into the NIC as
well. Taking the plunge of asking: couldn't "all queuing|wheeling"
necessary be consolidated to the sk buffs in NIC then? TCP buffer
windowing should be fairly agnostic to that, shouldn't it?
--
Besten Gruß
Matthias Tafelmeier
[-- Attachment #1.1.2: 0xE0164F5B8ADF343B.asc --]
[-- Type: application/pgp-keys, Size: 5250 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 538 bytes --]
prev parent reply other threads:[~2018-07-21 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 14:09 Dave Taht
2018-07-20 14:47 ` [Bloat] [Make-wifi-fast] " Luca Muscariello
2018-07-21 14:38 ` Jonathan Morton
2018-07-23 12:52 ` Mikael Abrahamsson
2018-07-23 15:36 ` Dave Taht
2018-07-23 17:26 ` dpreed
2018-07-21 13:19 ` Matthias Tafelmeier [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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9393eca9-3ac4-46cf-7737-89d1797db975@gmx.net \
--to=matthias.tafelmeier@gmx.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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