From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: xiangxia.m.yue@gmail.com, netdev@vger.kernel.org
Cc: Tonghao Zhang <xiangxia.m.yue@gmail.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Eric Dumazet <edumazet@google.com>,
Alexander Lobakin <alobakin@pm.me>,
Paolo Abeni <pabeni@redhat.com>,
Talal Ahmad <talalahmad@google.com>,
Kevin Hao <haokexin@gmail.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Kees Cook <keescook@chromium.org>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Antoine Tenart <atenart@kernel.org>, Wei Wang <weiwan@google.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [net-next v5 1/2] net: sched: use queue_mapping to pick tx queue
Date: Wed, 29 Dec 2021 16:13:50 -0300 [thread overview]
Message-ID: <87k0fn2pht.fsf@intel.com> (raw)
In-Reply-To: <20211220123839.54664-2-xiangxia.m.yue@gmail.com>
xiangxia.m.yue@gmail.com writes:
> From: Tonghao Zhang <xiangxia.m.yue@gmail.com>
>
> This patch fixes issue:
> * If we install tc filters with act_skbedit in clsact hook.
> It doesn't work, because netdev_core_pick_tx() overwrites
> queue_mapping.
>
> $ tc filter ... action skbedit queue_mapping 1
>
> And this patch is useful:
> * We can use FQ + EDT to implement efficient policies. Tx queues
> are picked by xps, ndo_select_queue of netdev driver, or skb hash
> in netdev_core_pick_tx(). In fact, the netdev driver, and skb
> hash are _not_ under control. xps uses the CPUs map to select Tx
> queues, but we can't figure out which task_struct of pod/containter
> running on this cpu in most case. We can use clsact filters to classify
> one pod/container traffic to one Tx queue. Why ?
>
> In containter networking environment, there are two kinds of pod/
> containter/net-namespace. One kind (e.g. P1, P2), the high throughput
> is key in these applications. But avoid running out of network resource,
> the outbound traffic of these pods is limited, using or sharing one
> dedicated Tx queues assigned HTB/TBF/FQ Qdisc. Other kind of pods
> (e.g. Pn), the low latency of data access is key. And the traffic is not
> limited. Pods use or share other dedicated Tx queues assigned FIFO Qdisc.
> This choice provides two benefits. First, contention on the HTB/FQ Qdisc
> lock is significantly reduced since fewer CPUs contend for the same queue.
> More importantly, Qdisc contention can be eliminated completely if each
> CPU has its own FIFO Qdisc for the second kind of pods.
>
> There must be a mechanism in place to support classifying traffic based on
> pods/container to different Tx queues. Note that clsact is outside of Qdisc
> while Qdisc can run a classifier to select a sub-queue under the
> lock.
One alternative, I don't know if it would work for you, it to use the
net_prio cgroup + mqprio.
Something like this:
* create the cgroup
$ mkdir -p /sys/fs/cgroup/net_prio/<CGROUP_NAME>
* assign priorities to the cgroup (per interface)
$ echo "<IFACE> <PRIO>" >> /sys/fs/cgroup/net_prio/<CGROUP_NAME>/net_prio.ifpriomap"
* use the cgroup in applications that do not set SO_PRIORITY
$ cgexec -g net_prio:<CGROUP_NAME> <application>
* configure mqprio
$ tc qdisc replace dev $IFACE parent root handle 100 mqprio \
num_tc 3 \
map 2 2 1 0 2 2 2 2 2 2 2 2 2 2 2 2 \
queues 1@0 1@1 2@2 \
hw 0
This would map all traffic with SO_PRIORITY 3 to TX queue 0, for example.
But I agree that skbedit's queue_mapping not working is unexpected and
should be fixed.
Cheers,
--
Vinicius
next prev parent reply other threads:[~2021-12-29 19:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 12:38 [net-next v5 0/2] net: sched: allow user to select txqueue xiangxia.m.yue
2021-12-20 12:38 ` [net-next v5 1/2] net: sched: use queue_mapping to pick tx queue xiangxia.m.yue
2021-12-20 13:57 ` Eric Dumazet
2021-12-20 14:21 ` Tonghao Zhang
2021-12-20 14:31 ` Tonghao Zhang
2021-12-20 17:51 ` Cong Wang
2021-12-22 1:19 ` Tonghao Zhang
2021-12-29 19:13 ` Vinicius Costa Gomes [this message]
2021-12-30 5:02 ` Tonghao Zhang
2022-01-26 19:58 ` Cong Wang
2022-01-27 1:35 ` Tonghao Zhang
2021-12-20 12:38 ` [net-next v5 2/2] net: sched: support hash/classid/cpuid selecting " xiangxia.m.yue
2021-12-20 17:57 ` Cong Wang
2021-12-22 1:23 ` Tonghao Zhang
2021-12-24 19:26 ` Cong Wang
2021-12-25 1:41 ` Tonghao Zhang
2021-12-29 12:50 ` Tonghao Zhang
2022-01-06 1:28 ` Tonghao Zhang
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=87k0fn2pht.fsf@intel.com \
--to=vinicius.gomes@intel.com \
--cc=alobakin@pm.me \
--cc=arnd@arndb.de \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haokexin@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=jonathan.lemon@gmail.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=talalahmad@google.com \
--cc=weiwan@google.com \
--cc=xiangxia.m.yue@gmail.com \
--cc=xiyou.wangcong@gmail.com \
/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).