On Mon, Apr 3, 2017 at 8:33 PM, Ricardo Farrington
wrote:
> Hi Sunil - this implementation was verified with multiple adapters installed.
> In this case, the field serves to differentiate the adapter.
>
>> LiquidIO---
>
> Rick
>
No, what I was referring to was, let's say there are two adap
To: Manlunas, Felix
Cc: David S. Miller ; Linux Netdev List
; Vatsavayi, Raghu ;
Chickles, Derek ; Burla, Satananda
; Ricardo Farrington
Subject: Re: [PATCH net-next] liquidio: use meaningful names for IRQs
On Tue, Mar 14, 2017 at 1:28 AM, Felix Manlunas
wrote:
> From: Rick Farrington
>
&
On Tue, Mar 14, 2017 at 1:28 AM, Felix Manlunas
wrote:
> From: Rick Farrington
>
> 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-
On Mon, 13 Mar 2017 12:58:04 -0700
Felix Manlunas wrote:
> From: Rick Farrington
>
> 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:
>
> Liq
> > 2. The IRQ name can only be specified at the time it is requested.
> > It cannot be changed after that.
Is there any inherent difficulty in adding that capability?
I.e., to rename the IRQ's action & kthread.
It would allow drivers to re-name their IRQ names upon NETDEV_CHANGENAME
From: Felix Manlunas
Date: Mon, 13 Mar 2017 12:58:04 -0700
> From: Rick Farrington
>
> 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:
>
> L
