netdev - Re: [PATCH net-next] net/mlx4_en: num cores tx rings for every UP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 17 May 2012 16:19:03 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	amirv@...lanox.com
Cc:	netdev@...r.kernel.org, oren@...lanox.com,
	john.r.fastabend@...el.com, liranl@...lanox.com
Subject: Re: [PATCH net-next] net/mlx4_en: num cores tx rings for every UP

From: Amir Vadai <amirv@...lanox.com>
Date: Thu, 17 May 2012 13:58:10 +0300

> Change the TX ring scheme such that the number of rings for untagged packets
> and for tagged packets (per each of the vlan priorities) is the same, unlike
> the current situation where for tagged traffic there's one ring per priority
> and for untagged rings as the number of core.
> 
> Queue selection is done as follows:
> 
> If the mqprio qdisc is operates on the interface, such that the core networking
> code invoked the device setup_tc ndo callback, a mapping of skb->priority =>
> queue set is forced - for both, tagged and untagged traffic.
> 
> Else, the egress map skb->priority =>  User priority is used for tagged traffic, and
> all untagged traffic is sent through tx rings of UP 0.
> 
> The patch follows the convergence of discussing that issue with John Fastabend
> over this thread http://comments.gmane.org/gmane.linux.network/229877
> 
> Cc: John Fastabend <john.r.fastabend@...el.com>
> Cc: Liran Liss <liranl@...lanox.com>
> Signed-off-by: Amir Vadai <amirv@...lanox.com>

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