linux-kernel - block device queues, elevatoring implicit or explicit?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGDaZ_pHn=ZHJ-cRy5am5w+EYpspfRTKvhmyDCcLVLH=T0Y2Sw@mail.gmail.com>
Date:	Sat, 16 Mar 2013 02:06:00 -0700
From:	Raymond Jennings <shentino@...il.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: block device queues, elevatoring implicit or explicit?

Are all block devices fundamentally elevators or fifos or what?

To be blunt, if a bunch of concurrent processes dump requests on a
noop queue, are they serviced fifo or in elevator order or what?

My goal is to get a dumb elevator that does nothing but sweep up and
down the disk mopping up outstanding requests as the disk heads ooze
across the sectors.
--
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/