On Thu, Mar 23, 2017 at 9:47 PM, Andy Lutomirski wrote:
> So don't we want queue id, not NAPI id? Or am I still missing something?
>
> But I'm also a but confused as to the overall performance effect.
> Suppose I have an rx queue that has its interrupt bound to cpu 0. For
> whatever reason (ran
On Thu, Mar 23, 2017 at 5:58 PM, Alexander Duyck
wrote:
> On Thu, Mar 23, 2017 at 3:43 PM, Andy Lutomirski wrote:
>> On Thu, Mar 23, 2017 at 2:38 PM, Alexander Duyck
>> wrote:
>>> From: Sridhar Samudrala
>>>
>>> This socket option returns the NAPI ID associated with the queue on which
>>> the l
On Thu, Mar 23, 2017 at 3:43 PM, Andy Lutomirski wrote:
> On Thu, Mar 23, 2017 at 2:38 PM, Alexander Duyck
> wrote:
>> From: Sridhar Samudrala
>>
>> This socket option returns the NAPI ID associated with the queue on which
>> the last frame is received. This information can be used by the apps t
On Thu, Mar 23, 2017 at 2:38 PM, Alexander Duyck
wrote:
> From: Sridhar Samudrala
>
> This socket option returns the NAPI ID associated with the queue on which
> the last frame is received. This information can be used by the apps to
> split the incoming flows among the threads based on the Rx qu
On Thu, 2017-03-23 at 14:38 -0700, Alexander Duyck wrote:
> From: Sridhar Samudrala
>
> This socket option returns the NAPI ID associated with the queue on which
> the last frame is received. This information can be used by the apps to
> split the incoming flows among the threads based on the Rx
From: Sridhar Samudrala
This socket option returns the NAPI ID associated with the queue on which
the last frame is received. This information can be used by the apps to
split the incoming flows among the threads based on the Rx queue on which
they are received.
If the NAPI ID actually represent
