From: David Ahern <dsahern@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
John Ousterhout <ouster@cs.stanford.edu>,
Andrew Lunn <andrew@lunn.ch>,
netdev@vger.kernel.org
Subject: Re: Bypass qdiscs?
Date: Mon, 6 Nov 2023 09:51:16 -0700 [thread overview]
Message-ID: <081c33fa-0fa7-4ac3-aadf-3036a24fd8a3@kernel.org> (raw)
In-Reply-To: <CAM0EoM=nzobHqxD45wf+DR-sAGSaxE2m-kUf__40-rekdkhhoA@mail.gmail.com>
On 11/6/23 9:17 AM, Jamal Hadi Salim wrote:
> BTW, Homa in-kernel instead of bypass is a better approach because you
> get the advantages of all other infra that the kernel offers..
yes. The memcpy that Homa currently needs (based on the netdevconf talk)
should be avoidable using the recent page pool work (RFCs).
next prev parent reply other threads:[~2023-11-06 16:51 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 [this message]
2023-11-08 16:50 ` John Ousterhout
2023-11-08 17:17 ` David Ahern
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=081c33fa-0fa7-4ac3-aadf-3036a24fd8a3@kernel.org \
--to=dsahern@kernel.org \
--cc=andrew@lunn.ch \
--cc=jhs@mojatatu.com \
--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).