From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] new installation (ssd, new udev, grub2)
Date: Fri, 10 Aug 2012 15:04:10 -0500 [thread overview]
Message-ID: <CAEH5T2Nv+W-FHvzc2k+0LCZ3yEJvb0q+BO3RZ1LV7tqd_2K==g@mail.gmail.com> (raw)
In-Reply-To: <20120810212213.0ce6e810@khamul.example.com>
On Fri, Aug 10, 2012 at 2:22 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> You also don't need an IO scheduler - ssd access is random like
> RAM, no heads moving in and out so no sector ordering to worry about.
> Configure the scheduler as NOOP in kernel config if all drives are ssd's
I've read some contradictory reports about the best scheduler for SSD.
Apparently some SSD controllers are tuned for sequential reads/writes
(drives that lean heavily on compression, I would imagine?) and for
those drives cfq or deadline may be the better choice. I would try
them all and use whatever works best for your workload.
next prev parent reply other threads:[~2012-08-10 20:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 14:25 [gentoo-user] new installation (ssd, new udev, grub2) Allan Gottlieb
2012-08-10 19:22 ` Alan McKinnon
2012-08-10 20:04 ` Paul Hartman [this message]
2012-08-12 18:20 ` Allan Gottlieb
2012-08-12 18:11 ` Allan Gottlieb
2012-08-12 19:44 ` Alan McKinnon
2012-08-13 12:52 ` Allan Gottlieb
2012-08-13 8:06 ` Neil Bothwick
2012-08-13 12:17 ` Michael Mol
2012-08-13 12:57 ` Neil Bothwick
2012-08-13 15:47 ` Alan McKinnon
2012-08-13 15:55 ` Michael Mol
2012-08-13 17:55 ` Pandu Poluan
2012-08-13 21:38 ` Alan McKinnon
2012-08-15 2:33 ` J.Marcos Sitorus
2012-08-15 16:42 ` Paul Hartman
2012-08-15 20:48 ` Mick
2012-08-15 21:14 ` Paul Hartman
2012-08-15 23:41 ` Neil Bothwick
2012-08-16 7:51 ` J.Marcos Sitorus
2012-08-16 14:55 ` Paul Hartman
2012-08-16 15:21 ` Pandu Poluan
2012-08-13 12:44 ` Allan Gottlieb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEH5T2Nv+W-FHvzc2k+0LCZ3yEJvb0q+BO3RZ1LV7tqd_2K==g@mail.gmail.com' \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox