From: David Ahern <dsahern@kernel.org>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Andrew Lunn <andrew@lunn.ch>,
netdev@vger.kernel.org
Subject: Re: Bypass qdiscs?
Date: Wed, 8 Nov 2023 10:17:27 -0700 [thread overview]
Message-ID: <89cd5f11-2c54-4905-b900-b1e06304805f@kernel.org> (raw)
In-Reply-To: <CAGXJAmz+j0y00XLc2YCyfK5aVPD12aDcrNzc58N1fExT6ceoVw@mail.gmail.com>
On 11/8/23 9:50 AM, John Ousterhout wrote:
> Hi David,
>
> Thanks for the suggestion, but if I understand this correctly, this
> will disable qdiscs for TCP as well as Homa; I suspect I shouldn't do
> that?
>
A means to separate issues - i.e., run Homa tests without qdisc overhead
or delays. You can worry about how to handle if/when you start
upstreaming the code.
next prev parent reply other threads:[~2023-11-08 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 23:55 Bypass qdiscs? John Ousterhout
2023-11-04 9:24 ` Ferenc Fejes
2023-11-04 15:08 ` Andrew Lunn
2023-11-05 2:47 ` John Ousterhout
2023-11-06 3:23 ` Stephen Hemminger
2023-11-06 4:27 ` David Ahern
2023-11-06 16:12 ` Jamal Hadi Salim
2023-11-06 16:17 ` Jamal Hadi Salim
2023-11-06 16:51 ` David Ahern
2023-11-08 16:50 ` John Ousterhout
2023-11-08 17:17 ` David Ahern [this message]
2023-11-09 17:50 ` David Laight
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=89cd5f11-2c54-4905-b900-b1e06304805f@kernel.org \
--to=dsahern@kernel.org \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=ouster@cs.stanford.edu \
--cc=stephen@networkplumber.org \
/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).