All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.r.fastabend@intel.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Anton 'EvilMan' Danilov <littlesmilingcloud@gmail.com>,
	netdev@vger.kernel.org
Subject: Re: Using HTB over MultiQ
Date: Fri, 08 Nov 2013 15:11:34 -0800	[thread overview]
Message-ID: <527D6FA6.5040508@intel.com> (raw)
In-Reply-To: <1383947802.16391.3.camel@edumazet-glaptop2.roam.corp.google.com>

On 11/8/2013 1:56 PM, Eric Dumazet wrote:
> On Fri, 2013-11-08 at 19:53 +0400, Anton 'EvilMan' Danilov wrote:
>
>> Hm.. I think I need another way to classify packets for using of mq
>> qdisc, because it don't support classify at root (not supported error
>> on try attach filter).
>
> I think it might be time to add filters on the device, and run them
> without any lock (rcu protection only)
>
> John, I think you had some previous work ?

Yes, I have a net-next fork with this but I currently introduced a bug
in the u32 classifier. I'll resurrect this next week and send something
out. We can take a look and see if its useful.

>
>> On next week i'll try to write ipset extension for setting of priority
>> and queue_mapping value through the IPSET netfilter target.
>
> Sounds a nice idea as well.
>

Another thought would be to put a netfilter hook above the qdisc and on
ingress (not in the bridge module). I've been meaning to take a look
at nftables I'm not sure how much duplication exists between nftables
and tc classifiers at this point.

>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2013-11-08 23:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 13:12 Using HTB over MultiQ Anton 'EvilMan' Danilov
2013-11-07 13:49 ` Sergey Popovich
2013-11-07 16:13   ` Eric Dumazet
2013-11-07 14:11 ` Eric Dumazet
2013-11-07 14:20   ` Eric Dumazet
2013-11-07 14:39     ` John Fastabend
2013-11-07 14:54       ` Eric Dumazet
2013-11-07 15:06         ` John Fastabend
2013-11-07 15:17           ` John Fastabend
2013-11-07 16:10             ` Eric Dumazet
2013-11-08 14:53       ` Anton 'EvilMan' Danilov
2013-11-08 15:07         ` Eric Dumazet
2013-11-08 15:11           ` John Fastabend
2013-11-08 15:53             ` Anton 'EvilMan' Danilov
2013-11-08 21:56               ` Eric Dumazet
2013-11-08 23:11                 ` John Fastabend [this message]
2013-11-08 17:55             ` Eric Dumazet
2013-11-08 20:01               ` Eric Dumazet
     [not found]           ` <CAEzD07LmzCtVWM4wnq57N+NfqDUK3bLWDisSceyPfg4MiWz5=Q@mail.gmail.com>
2013-11-08 16:11             ` Fwd: " Anton 'EvilMan' Danilov
2013-11-07 14:29 ` Eric Dumazet

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=527D6FA6.5040508@intel.com \
    --to=john.r.fastabend@intel.com \
    --cc=eric.dumazet@gmail.com \
    --cc=littlesmilingcloud@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.