linux-kernel - Re: Implementing NVMHCI...

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

Message-ID: <49E0FBC6.3050600@garzik.org>
Date:	Sat, 11 Apr 2009 16:21:26 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Linux IDE mailing list <linux-ide@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Jens Axboe <jens.axboe@...cle.com>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: Implementing NVMHCI...

Linus Torvalds wrote:
> 
> On Sat, 11 Apr 2009, Alan Cox wrote:
>>> 	  The spec describes the sector size as
>>> 	  "512, 1k, 2k, 4k, 8k, etc."   It will be interesting to reach
>>> 	  "etc" territory.
>> Over 4K will be fun.
> 
> And by "fun", you mean "irrelevant".
> 
> If anybody does that, they'll simply not work. And it's not worth it even 
> trying to handle it.

FSVO trying to handle...

At the driver level, it would be easy to clamp sector size to 4k, and 
point the scatterlist to a zero-filled region for the >4k portion of 
each sector.  Inefficient, sure, but it is low-cost to the driver and 
gives the user something other than a brick.

	if (too_large_sector_size)
		nvmhci_fill_sg_clamped_interleave()
	else
		nvmhci_fill_sg()

Regards,

	Jeff



--
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/