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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 05 Jan 2015 13:10:14 +0800
From:	Jason Wang <>
To:	Rusty Russell <>,,,
Subject: Re: [RFC PATCH 0/3] Sharing MSIX irq for tx/rx queue pairs

On 01/05/2015 09:39 AM, Rusty Russell wrote:
> Jason Wang <> writes:
>> Hi all:
>> This series try to share MSIX irq for each tx/rx queue pair. This is
>> done through:
>> - introducing virtio pci channel which are group of virtqueues that
>>   sharing a single MSIX irq (Patch 1)
>> - expose channel setting to virtio core api (Patch 2)
>> - try to use channel setting in virtio-net (Patch 3)
> Hi Jason,
>         Is "channel" a term you created yourself, or something I was
> just unaware of?  

By myself and probably not accurate.
> irq_group would seem more obvious, if the former.

Yes, will use this in next version. Thanks.
>> For the transport that does not support channel, channel paramters
>> were simply ignored. For devices that does not use channel, it can
>> simply pass NULL or zero to virito core.
>> With the patch, 1 MSIX irq were saved for each TX/RX queue pair.
> It seems fairly straightforward.
> Acked-by: Rusty Russell <>
> Thanks,
> Rusty.
> --

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists