| 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
| ||
|
Message-ID: <54AA1CB6.9020109@redhat.com> Date: Mon, 05 Jan 2015 13:10:14 +0800 From: Jason Wang <jasowang@...hat.com> To: Rusty Russell <rusty@...tcorp.com.au>, mst@...hat.com, virtualization@...ts.linux-foundation.org, linux-kernel@...r.kernel.org 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 <jasowang@...hat.com> 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 <rusty@...tcorp.com.au> > > Thanks, > Rusty. > -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists