netdev - Re: flow director and packet ordering

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: <20090616.023132.194401812.davem@davemloft.net>
Date:	Tue, 16 Jun 2009 02:31:32 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	peter.p.waskiewicz.jr@...el.com
Cc:	netdev@...r.kernel.org, jeffrey.t.kirsher@...el.com,
	jesse.brandeburg@...el.com
Subject: Re: flow director and packet ordering

From: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
Date: Mon, 15 Jun 2009 23:42:16 -0700 (Pacific Daylight Time)

> The way the internal hashing works in the software and hardware, I think 
> we're pretty safe with getting moved unexpectedely.

The device RX being empty doesn't mean anything.

Those packets, even after you give them all to netif_receive_skb(),
can be held up in all number of queues, or even scheduled off to be
processed by ksoftirqd after a full context switch.

In the meantime you cannot switch the RX queue mapping without
introducing reordering.

So my original fears and doubts still stand :-)
--
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