Date: Mon, 22 Mar 2010 08:23:43 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Andriy Gapon <avg@icyb.net.ua> Cc: Alexander Motin <mav@FreeBSD.org>, freebsd-current@FreeBSD.org, Ivan Voras <ivoras@FreeBSD.org>, freebsd-arch@FreeBSD.org Subject: Re: Increasing MAXPHYS Message-ID: <5754.1269246223@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 21 Mar 2010 16:56:32 %2B0200." <4BA633A0.2090108@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <4BA633A0.2090108@icyb.net.ua>, Andriy Gapon writes: >on 21/03/2010 16:05 Alexander Motin said the following: >> Ivan Voras wrote: >>> Hmm, it looks like it could be easy to spawn more g_* threads (and, >>> barring specific class behaviour, it has a fair chance of working out of >>> the box) but the incoming queue will need to also be broken up for >>> greater effect. >> >> According to "notes", looks there is a good chance to obtain races, as >> some places expect only one up and one down thread. > >I haven't given any deep thought to this issue, but I remember us discussing >them over beer :-) The easiest way to obtain more parallelism, is to divide the mesh into multiple independent meshes. This will do you no good if you have five disks in a RAID-5 config, but if you have two disks each mounted on its own filesystem, you can run a g_up & g_down for each of them. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5754.1269246223>