linux-kernel - Re: [PATCH 1/2] Avoid bio

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-prev] [day] [month] [year] [list]

Date:	Fri, 4 Jul 2008 09:11:36 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Mikulas Patocka <mpatocka@...hat.com>
Cc:	Jens Axboe <jens.axboe@...cle.com>, linux-kernel@...r.kernel.org,
	Neil Brown <neilb@...e.de>
Subject: Re: [PATCH 1/2] Avoid bio_endio recursion

> That statement is true for any two block device protocol. Then, why 

Not it isn't. The mentality of quite a few devices is very different to
SCSI in the way the express queueing and caching. You cannot for example
map I2O Block onto SCSI at all.

> doesn't Linux use SCSI for all block devices? --- add scsi command block 
> to struct bio and we can pass them directly to controller driver 

That was discussed, along with continuing to split scsi and block aspects
of queueing, tagging and error recovery apart. Windows btw does generally
follow that 'everything is SCSI' approach
--
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/