From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: davem@davemloft.net, john.fastabend@gmail.com,
eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net, sched: add clsact qdisc
Date: Thu, 7 Jan 2016 09:29:52 -0500 [thread overview]
Message-ID: <568E7660.1070801@mojatatu.com> (raw)
In-Reply-To: <568E52E8.1010804@iogearbox.net>
On 16-01-07 06:58 AM, Daniel Borkmann wrote:
> On 01/07/2016 11:09 AM, Hannes Frederic Sowa wrote:
>
> Idea was that this is done before we pick txq as stated. F.e., could also
> be that we end up not having enqueue handler, thus moving this further down
> (not sure if there's a good place?), might make it all more scattered resp.
> complex to cover all parts.
>
From a cursory glance (Will comment a lot more later, definetely bt
netdev11 time):
I like the idea - actually i think that this is where John was heading
initially. Both efforts complement each other.
This scheme could be used to compensate for the queue lock avoidance
and do a direct txmit (and let the hardware do the scheduling).
The classid selection could clearly be done at this early stage.
And a few of the standard skb metadatum could be used to map to
hardware offloading.
cheers,
jamal
next prev parent reply other threads:[~2016-01-07 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 1:00 [PATCH net-next] net, sched: add clsact qdisc Daniel Borkmann
2016-01-06 2:40 ` Cong Wang
2016-01-07 3:53 ` Alexei Starovoitov
2016-01-07 10:09 ` Hannes Frederic Sowa
2016-01-07 11:58 ` Daniel Borkmann
2016-01-07 14:29 ` Jamal Hadi Salim [this message]
2016-01-07 14:42 ` Hannes Frederic Sowa
2016-01-07 15:16 ` Daniel Borkmann
2016-01-07 16:29 ` Eric Dumazet
2016-01-07 16:52 ` Daniel Borkmann
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=568E7660.1070801@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.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).