| 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 PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 15 Sep 2014 11:23:09 +0200 From: Roger Pau Monné <roger.pau@...rix.com> To: Arianna Avanzini <avanzini.arianna@...il.com>, <konrad.wilk@...cle.com>, <boris.ostrovsky@...cle.com>, <david.vrabel@...rix.com>, <xen-devel@...ts.xenproject.org>, <linux-kernel@...r.kernel.org> CC: <axboe@...com>, <felipe.franciosi@...rix.com> Subject: Re: [Xen-devel] [PATCH RFC 0/4] Multi-queue support for xen-blkfront and xen-blkback El 22/08/14 a les 13.20, Arianna Avanzini ha escrit: > Hello, [...] > The patchset implements in the backend driver the retrieval of information > about the currently-in-use block layer API for a certain device and about > the number of available submission queues, if the API turns out to be the > multi-queue one. The information is then advertised to the frontend driver > via XenStore. The frontend device can exploit such an information to allocate > and grant multiple I/O rings that the backend will be able to map. > The patchset has been tested with fio's IOmeter emulation on a four-cores > machine with a null_blk device (some results are available here: [2]). Have you tried if using multiple queues (rings) between blkfront and blkback even when the underlying device doesn't use MQ increases the throughput? Roger. -- 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