[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <717fbdd6-9ef7-3ad6-0c29-d0f3798ced8e@intel.com>
Date: Wed, 12 Jul 2023 13:09:35 -0700
From: "Nambiar, Amritha" <amritha.nambiar@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: <netdev@...r.kernel.org>, <davem@...emloft.net>,
<sridhar.samudrala@...el.com>
Subject: Re: [net-next/RFC PATCH v1 1/4] net: Introduce new napi fields for
rx/tx queues
On 6/2/2023 11:06 PM, Jakub Kicinski wrote:
> On Thu, 01 Jun 2023 10:42:25 -0700 Amritha Nambiar wrote:
>> Introduce new napi fields 'napi_rxq_list' and 'napi_txq_list'
>> for rx and tx queue set associated with the napi and
>> initialize them. Handle their removal as well.
>>
>> This enables a mapping of each napi instance with the
>> queue/queue-set on the corresponding irq line.
>
> Wouldn't it be easier to store the NAPI instance pointer in the queue?
> That way we don't have to allocate memory.
>
Could you please elaborate on this so I have more clarity ? Are you
suggesting that there's a way to avoid maintaining the list of queues in
the napi struct?
The idea was for netdev-genl to extract information out of
netdev->napi_list->napi. For tracking queues, we build a linked list of
queues for the napi and store it in the napi_struct. This would also
enable updating the napi<->queue[s] association (later with the 'set'
command), i.e. remove the queue[s] from the existing napi instance that
it is currently associated with and map with the new napi instance, by
simply deleting from one list and adding to the new list.
Powered by blists - more mailing lists