linux-kernel - Re: [PATCH 0/2] Configurable max discard size

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20150714175317.GA30609@lst.de>
Date:	Tue, 14 Jul 2015 19:53:17 +0200
From:	Christoph Hellwig <hch@....de>
To:	Jens Axboe <axboe@...com>
Cc:	Christoph Hellwig <hch@....de>, linux-kernel@...r.kernel.org,
	snitzer@...hat.com
Subject: Re: [PATCH 0/2] Configurable max discard size

On Tue, Jul 14, 2015 at 10:04:12AM -0600, Jens Axboe wrote:
> Based on experimentation with two different vendors, 64MB would be a good 
> default. Question is how best to set that. At least with the current patch, 
> untouched, 'discard_max_bytes' will still show the hw max value. If I 
> default it to 64MB, we'd lose that information until people started bumping 
> it up in size. Maybe that's not such a big deal, however.

Just expose the max value as another read-only sysfs value?
--
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/