netdev - Re: [RFC] NAPI as kobject proposal

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]

Message-Id: <20100203.181716.29531795.davem@davemloft.net>
Date:	Wed, 03 Feb 2010 18:17:16 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	shemminger@...tta.com
Cc:	netdev@...r.kernel.org
Subject: Re: [RFC] NAPI as kobject proposal

From: Stephen Hemminger <shemminger@...tta.com>
Date: Wed, 3 Feb 2010 17:58:46 -0800

> The usage model I see is wanting to have:
>   1. only some cores being used for receive traffic
>      on single Rx devices (NAPI)
>   2. only some cores being used for receive traffic
>      on legacy devices (non-NAPI)
>   3. being able to configure a set of cpus with same   
>      IRQ/cache when doing Rx multi-queue.  Assign MSI-X
>      IRQ per core and allow both HT on core to split
>      that RX traffic.
> 
> All this should be manageable by some user utility like irqbalance.
> 
> #1 and #2 argue for a per device map (like irq_affinity) but
> #3 is harder; not sure the right API for that.

Do you think the people setting RPS maps aren't capable of
configuring IRQ affinities? :-)
--
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