netdev - Re: Why do we use RX queue mapping for TX?

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHA+R7N=uFyja4daQTY50RVMAzYT1J1AUMmsF+6HynZQED+OgA@mail.gmail.com>
Date:	Fri, 20 Feb 2015 10:09:44 -0800
From:	Cong Wang <cwang@...pensource.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	"David S. Miller" <davem@...emloft.net>,
	netdev <netdev@...r.kernel.org>
Subject: Re: Why do we use RX queue mapping for TX?

On Wed, Feb 18, 2015 at 4:16 PM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> On Wed, 2015-02-18 at 15:57 -0800, Cong Wang wrote:
>
>> I am aware of it. I even would guess (means not digging the history)
>> skb_edit was invented for bonding queue mapping, since I don't see it
>> even works as a general TC action on the physical interface. We pick
>> the tx queue prior to getting the Qdisc, therefore too late to set
>> skb->queue_mapping to specify a hardware TX queue. This is
>> another story I planned to bring it up to David.
>
> skbedit can be done on ingress I presume.
>

Yes of course, but that means I need an indirect layer to
map RX to TX (ifb or mirred), since I only care about TX queues. :-/
--
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