netdev - Re: [PATCH net-next 4/4] ionic: separate interrupt for Tx and Rx

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 27 Jul 2020 09:37:45 -0700
From:   Shannon Nelson <snelson@...sando.io>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     netdev@...r.kernel.org, davem@...emloft.net
Subject: Re: [PATCH net-next 4/4] ionic: separate interrupt for Tx and Rx

On 7/24/20 5:56 PM, Jakub Kicinski wrote:
> On Fri, 24 Jul 2020 17:23:26 -0700 Shannon Nelson wrote:
>> Add the capability to split the Tx queues onto their own
>> interrupts with their own napi contexts.  This gives the
>> opportunity for more direct control of Tx interrupt
>> handling, such as CPU affinity and interrupt coalescing,
>> useful for some traffic loads.
>>
>> To enable, use the ethtool private flag:
>> 	ethtool --set-priv-flag enp20s0 split-q-intr on
>> To restore defaults
>> 	ethtool --set-priv-flag enp20s0 split-q-intr off
>>
>> When enabled, the number of queues is cut in half in order
>> to reuse the interrupts that have already been allocated to
>> the device.  When disabled, the queue count is restored.
>>
>> Signed-off-by: Shannon Nelson <snelson@...sando.io>
> Splitting queues into tx-only and rx-only is done like this:
>
> ethtool -L enp20s0 rx N tx N combined 0
>
> And then back to combined:
>
> ethtool -L enp20s0 rx 0 tx 0 combined N
>
> No need for a private flag here.

Sure, we can do it that way.

Thanks,
sln