Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Jul 2012 15:31:51 +0200
From:      Ivan Voras <ivoras@freebsd.org>
To:        freebsd-geom@freebsd.org
Cc:        freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org
Subject:   Re: geom <-> cam disk
Message-ID:  <jurgs7$a1r$1@dough.gmane.org>
In-Reply-To: <501074E4.4040805@FreeBSD.org>
References:  <501056C4.3080806@FreeBSD.org> <50106E5F.4030402@FreeBSD.org> <501074E4.4040805@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigF19539FA2CE033B976BD1189
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 26/07/2012 00:36, Andriy Gapon wrote:
> on 26/07/2012 01:08 Alexander Motin said the following:
>> Different controllers have different command queueing limitations. If =
you are
>> testing with ahci(4) driver and modern disks, then their 32 command sl=
ots per
>> port can be enough for many workloads to enqueue all commands to the h=
ardware
>> and leave queue empty as you've described. But if you take harder work=
load, or
>> controller/ device without command queueing support, extra requests wi=
ll be
>> accumulated on that bioq and sorted there.
>=20
> Alexander,
>=20
> thank you for the reply.
> Indeed, using 64 parallel dd processes with bs=3D512 I was able to 'kic=
k in' the
> disksort logic.  But I am not sure if the disksort algorithm makes much=

> difference in this case given the number of commands that a disk firmwa=
re can
> internally re-order.  (Not mentioning that potentially disksort could s=
tarve
> some I/O bound processes in favor of others -- but that's a totally dif=
ferent
> topic).

Is the queue drained in-order (i.e. after sorting)? Then it could help
as the device queues will be filled with requests whose offsets are
closer together (as opposed to totally random), which helps with bursts
(e.g. untarring the ports tree).


--------------enigF19539FA2CE033B976BD1189
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlARRscACgkQ/QjVBj3/HSy7SACeJEx+tZfRdo2stam9R4hWNCUL
NzYAnR00QKCAvhtJ3FJ4vAZ3TIf0vZOL
=twL2
-----END PGP SIGNATURE-----

--------------enigF19539FA2CE033B976BD1189--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?jurgs7$a1r$1>