From: John Fastabend <john.r.fastabend@intel.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Anton 'EvilMan' Danilov <littlesmilingcloud@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Using HTB over MultiQ
Date: Thu, 07 Nov 2013 06:39:59 -0800 [thread overview]
Message-ID: <527BA63F.7040900@intel.com> (raw)
In-Reply-To: <1383834021.9412.61.camel@edumazet-glaptop2.roam.corp.google.com>
On 11/7/2013 6:20 AM, Eric Dumazet wrote:
> On Thu, 2013-11-07 at 06:11 -0800, Eric Dumazet wrote:
>> On Thu, 2013-11-07 at 17:12 +0400, Anton 'EvilMan' Danilov wrote:
>>> Hello.
>>>
>>> I'm experimenting with high performance linux router with 10G NICs.
>>> On high traffic rates the performance are limited by the lock of root
>>> queue discipline. For avoid impact of locking i've decided to build
>>> QoS scheme over the multiq qdisc.
>>>
>
> Oh well, this is a router.
>
> So I think you need to change the device queue selection so that it only
> depends on your filters / htb classes.
>
> Otherwise flows for a particular 'customer' might be spread on the 8
> queues, so the rate could be 8 * 1Mbit, instead of 1Mbit.
>
With the multiq qdisc you could attach filter to the root qdisc and use
skbedit to set the queue_mapping field,
#tc filter add dev eth0 parent 1: protocol ip prio 1 u32 \
match ip dst 192.168.0.3 \
action skbedit queue_mapping 3
if you configure the filters to map to the correct classes this would
work.
Or another way would be use mqprio and steer packets to HTB classes
using the skb->priority. The priority can be set by iptables/nftables
or an ingress filter.
.John
next prev parent reply other threads:[~2013-11-07 14:40 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 [this message]
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
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=527BA63F.7040900@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 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).