netdev - Re: [PATCH 1/4]: net: Allow RX queue selection to seed TX queue hashing.

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:	Wed, 28 Jan 2009 21:01:42 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	herbert@...dor.apana.org.au
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 1/4]: net: Allow RX queue selection to seed TX queue
 hashing.

From: Herbert Xu <herbert@...dor.apana.org.au>
Date: Thu, 29 Jan 2009 15:41:48 +1100

> But yeah if a single TX queue isn't big enough to take care of
> the output from a single core then you will need multiple TX
> queues.  Although from an system-wide point of view it would
> seem to be more optimal to make that TX queue bigger rather than
> forcing the software to use multiple queues (which may come with
> a bigger overhead) to make up for it.
> 
> Of course for us software developers we don't really have a choice :)

Yes, this is one of the things I told Robert, make the
TX queues larger :-)

Besides, a plain iterating RX --> TX function can't work because
that doesn't take flows into consideration and thus can introduce
reordering.
--
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