[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170320081530.0f4cdbee@xeon-e3>
Date: Mon, 20 Mar 2017 08:15:30 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Felix Manlunas <felix.manlunas@...ium.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
raghu.vatsavayi@...ium.com, derek.chickles@...ium.com,
satananda.burla@...ium.com, ricardo.farrington@...ium.com
Subject: Re: [PATCH net-next] liquidio: use meaningful names for IRQs
On Mon, 13 Mar 2017 12:58:04 -0700
Felix Manlunas <felix.manlunas@...ium.com> wrote:
> From: Rick Farrington <ricardo.farrington@...ium.com>
>
> All IRQs owned by the PF and VF drivers share the same nondescript name
> "octeon"; this makes it difficult to setup interrupt affinity.
>
> Change the IRQ names to reflect their specific purpose:
>
> LiquidIO<id>-<func>-<type>-<queue pair num>
>
> Examples:
> LiquidIO0-pf0-rxtx-3
> LiquidIO1-vf1-rxtx-0
> LiquidIO0-pf0-aux
>
> We cannot use netdev->name for naming the IRQs because:
>
> 1. Early during init, the PF and VF drivers require interrupts to
> send/receive control data from the NIC firmware; so the PF and VF
> must request IRQs long before the netdev struct is registered.
>
> 2. The IRQ name can only be specified at the time it is requested.
> It cannot be changed after that.
>
> Signed-off-by: Rick Farrington <ricardo.farrington@...ium.com>
> Signed-off-by: Felix Manlunas <felix.manlunas@...ium.com>
> Signed-off-by: Satanand Burla <satananda.burla@...ium.com>
Irqbalance used to parse the interrupt names and expect the network device name.
Powered by blists - more mailing lists