| 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
| ||
|
Date: Thu, 16 Apr 2009 21:56:30 +0900 (JST) From: Ryo Tsuruta <ryov@...inux.co.jp> To: vgoyal@...hat.com Cc: dm-devel@...hat.com, vivek.goyal2008@...il.com, linux-kernel@...r.kernel.org, agk@...hat.com Subject: Re: [dm-devel] Re: dm-ioband: Test results. Hi Vivek, > How does your ioband setup looks like. Have you created at least one more > competing ioband device? Because I think only in that case you have got > this ad-hoc logic of waiting for the group which has not finished the > tokens yet and you will end up buffering the bio in a FIFO. I created two ioband devices and ran the dd commands only on the first device. > Do let me know if you think there is something wrong with my > configuration. >From a quick look at your configuration, there seems to be no problem. > Can you also send bio-cgroup patches which apply to 2.6.30-rc1 so that > I can do testing for async writes. I've just posted the patches to related mailing lists. Please try it. > Why have you split the regular patch and bio-cgroup patch? Do you want > to address only reads and sync writes? For the first step, my goal is to merge dm-ioband into device-mapper, and bio-cgroup is not necessary for all situations such as bandwidth control on a per partition basis. I'll also try to do more test and report you back. Thank you for your help, Ryo Tsuruta -- 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