netdev - Re: [PATCH 20/31]: pkt_sched: Perform bulk of qdisc destruction in RCU.

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: <20080721.082627.128593651.davem@davemloft.net>
Date:	Mon, 21 Jul 2008 08:26:27 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	herbert@...dor.apana.org.au
Cc:	hadi@...erus.ca, kaber@...sh.net, netdev@...r.kernel.org,
	johannes@...solutions.net, linux-wireless@...r.kernel.org
Subject: Re: [PATCH 20/31]: pkt_sched: Perform bulk of qdisc destruction in
 RCU.

From: Herbert Xu <herbert@...dor.apana.org.au>
Date: Mon, 21 Jul 2008 23:22:20 +0800

> On Mon, Jul 21, 2008 at 08:09:01AM -0700, David Miller wrote:
> >
> > > Actually you've hit it on the head, as an alternative to TX hashing
> > > on the packet content, we need to allow TX queue selection based on
> > > the current CPU ID.
> > 
> > This we should avoid, it would allow reordering within a flow.
> 
> Not if the RX hashing is flow-based...

Can you control the process scheduler and where it decides
to run the processing running sendmsg() too?

That's the problem.

It is totally unwise to do CPU based TX hashing.
--
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