From: Jamal Hadi Salim <jhs@mojatatu.com>
To: David Ahern <dsahern@kernel.org>
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 11:17:38 -0500 [thread overview]
Message-ID: <CAM0EoM=nzobHqxD45wf+DR-sAGSaxE2m-kUf__40-rekdkhhoA@mail.gmail.com> (raw)
In-Reply-To: <CAM0EoMm+x2eOVbn_NMDYVu4tEjccvvHObt0OSPvCibMAfiNs5w@mail.gmail.com>
On Mon, Nov 6, 2023 at 11:12 AM Jamal Hadi Salim <jhs@mojatatu.com> wrote:
>
> On Sun, Nov 5, 2023 at 11:27 PM David Ahern <dsahern@kernel.org> wrote:
> >
> > On 11/5/23 8:23 PM, Stephen Hemminger wrote:
> > > On Sat, 4 Nov 2023 19:47:30 -0700
> > > John Ousterhout <ouster@cs.stanford.edu> wrote:
> > >
> > >> I haven't tried creating a "pass through" qdisc, but that seems like a
> > >> reasonable approach if (as it seems) there isn't something already
> > >> built-in that provides equivalent functionality.
> > >>
> > >> -John-
> > >>
> > >> P.S. If hardware starts supporting Homa, I hope that it will be
> > >> possible to move the entire transport to the NIC, so that applications
> > >> can bypass the kernel entirely, as with RDMA.
> > >
> > > One old trick was setting netdev queue length to 0 to avoid qdisc.
> > >
> >
> > tc qdisc replace dev <name> root noqueue
> >
> > should work
>
> John,
> IIUC, Homa transmit is done by a pacer that ensures the packets are
> scheduled without forming the queues in the NIC. So what David said
> above should be sufficient setup.
BTW, Homa in-kernel instead of bypass is a better approach because you
get the advantages of all other infra that the kernel offers..
cheers,
jamal
> cheers,
> jamal
> >
next prev parent reply other threads:[~2023-11-06 16: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 [this message]
2023-11-06 16:51 ` David Ahern
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='CAM0EoM=nzobHqxD45wf+DR-sAGSaxE2m-kUf__40-rekdkhhoA@mail.gmail.com' \
--to=jhs@mojatatu.com \
--cc=andrew@lunn.ch \
--cc=dsahern@kernel.org \
--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).