Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Mar 2010 16:56:32 +0200
From:      Andriy Gapon <avg@icyb.net.ua>
To:        Alexander Motin <mav@FreeBSD.org>
Cc:        freebsd-current@FreeBSD.org, Ivan Voras <ivoras@FreeBSD.org>, freebsd-arch@FreeBSD.org
Subject:   Re: Increasing MAXPHYS
Message-ID:  <4BA633A0.2090108@icyb.net.ua>
In-Reply-To: <4BA6279E.3010201@FreeBSD.org>
References:  <1269109391.00231800.1269099002@10.7.7.3>	<1269120182.00231865.1269108002@10.7.7.3>	<1269120188.00231888.1269109203@10.7.7.3>	<1269123795.00231922.1269113402@10.7.7.3>	<1269130981.00231933.1269118202@10.7.7.3>	<1269130986.00231939.1269119402@10.7.7.3>	<1269134581.00231948.1269121202@10.7.7.3>	<1269134585.00231959.1269122405@10.7.7.3> <4BA6279E.3010201@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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 :-)
I think one idea was making sure (somehow) that requests traveling over the same
edge of a geom graph (in the same direction) do it using the same queue/thread.
Another idea was to bring some netgraph-like optimization where some (carefully
chosen) geom vertices pass requests by a direct call instead of requeuing.

-- 
Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BA633A0.2090108>