netdev - Re: [PATCH 0/3] Add support for rx flow hash configuration in a network device

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]

Date:	Sun, 29 Jun 2008 13:49:36 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	andi@...stfloor.org
Cc:	Santwona.Behera@....COM, netdev@...r.kernel.org, jeff@...zik.org,
	Matheos.Worku@....COM, Michael.Speer@....COM,
	gkernel-commit@...ts.sourceforge.net
Subject: Re: [PATCH 0/3] Add support for rx flow hash configuration in a
 network device

From: Andi Kleen <andi@...stfloor.org>
Date: Sun, 29 Jun 2008 14:17:56 +0200

> Are you sure ethtool is the right interface for this?

Yes.

> Me thinks the kernel should just do the right thing automatically
> for this, by distributing the flows over CPUs.

How the work, and what kind of work, should be distributed across the
machine is the user's business.

Or maybe we should just get rid of all of those NUMA knobs we have
too?

We've discussed this before and Jeff Garzik and I already told
everyone that we want to make this configurable and ethtool is
the way to do it no matter how adhoc and device specific the
interfaces might end up being.

Please don't send submitters mixed messages like this after we've
told them to do things this way, it only leads to discouragement
for new contributors.
--
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