linux-kernel - Re: libata: set queue SSD flag for SSD devices

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: <20081011090407.6de9b8b4@infradead.org>
Date:	Sat, 11 Oct 2008 09:04:07 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
Cc:	Jens Axboe <jens.axboe@...cle.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-ide@...r.kernel.org, torvalds@...l.org
Subject: Re: libata: set queue SSD flag for SSD devices

On Sat, 11 Oct 2008 17:44:13 +0200
James Bottomley <James.Bottomley@...senPartnership.com> wrote:

> 
> > So we need something a bit more involved, but not too complex. A
> > fine line...
> 
> It's a policy ... just let userspace do it so the user can tune it.
> That's what EMC does now (except I think they key of inquiry strings
> rather than cache size).


while the chosen elevator obviously is policy, the kernel really should
pick a sensible default based on what it knows.
Lets put it this way: if userland needs to do a tuning to the kernel
based on data only provided by the kernel, and will always do it the
same way, we should have made that choice the default policy in the
kernel in the first place.

-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/