netdev - Re: [PATCH 1/5] soreuseport: infrastructure

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CA+mtBx9n5KQuBxy7V7bNiXRs0NNUo7mk+O6txeJWeUsXmODKow@mail.gmail.com>
Date:	Sun, 20 Jan 2013 15:33:35 -0800
From:	Tom Herbert <therbert@...gle.com>
To:	PJ Waskiewicz <WaskiewiczJr@...gle.com>
Cc:	Eric Dumazet <eric.dumazet@...il.com>,
	Stephen Hemminger <stephen@...workplumber.org>,
	netdev@...r.kernel.org, davem@...emloft.net,
	netdev@...kandruth.co.uk
Subject: Re: [PATCH 1/5] soreuseport: infrastructure

> It would be pretty neat if the CPU layout could make it to this level, so
> that you could choose queues based on the shared cache layout.  e.g. if
> cores 0 and 2 shared the same L2 cache, then you can be intelligent about
> landing flows on those queues bound to those cores.  Essentially the info
> that feeds the cpuid utility being used to make even smarter decisions of
> flow tuning.
>
Indeed.  I think Ben's cpu_rmap code already pretty much does this...

> Cheers,
> -PJ
--
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