public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Optimizations for SSD netbook
Date: Sat, 30 May 2009 10:04:54 -0700	[thread overview]
Message-ID: <49bf44f10905301004v775f019ai8080a9b47776deb5@mail.gmail.com> (raw)
In-Reply-To: <20090530203830.3789a94f@coercion>

>> >> 2. added elevator=noop as a boot parameter
>> >
>> > I remember that I've given this second advice. Since then I've read in
>> > the German computer journal c't [1] that CFQ has a detection for SSDs
>> > since 2.6.28 and now is the best choice for these devices.
>>
>> OK, do I need a boot parameter if I've set CFQ as the default IO
>> scheduler in the kernel config?
>
> No, that's what default switch is there for.
>
>
>> > Yup, the entry should read:
>> > tmp /tmp tmpfs default 0 0
>
> I'd also suggest to explicitly specify max size of tmpfs mount, since
> system locking because of wrong cp command is probably the last thing
> you want. Argument is "size=" (see man 8 mount).
>
>
>> Do you think mounting /tmp in RAM is worthwhile?  Mike doesn't seem to
>> think too highly of it.
>
> I guess accelerated fsync and reduced disk wear should be a nice plus
> for SSD device, provided the path in question is constanly used for
> writing which really might be the case with files, created in /tmp by
> various mktemp implementations (like python's) which I haven't really
> thought about, so I think I might be wrong about the issue here, sorry.

Thanks guys.  I think the /tmp trick made a good difference.  The last
thing I can think of is pruning the kernel way down.  I think it's
mostly default.

- Grant



  reply	other threads:[~2009-05-30 17:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30  0:24 [gentoo-user] Optimizations for SSD netbook Grant
2009-05-30  4:33 ` Mike Kazantsev
2009-05-30 11:59 ` Florian Philipp
2009-05-30 14:08   ` Grant
2009-05-30 14:38     ` Mike Kazantsev
2009-05-30 17:04       ` Grant [this message]
2009-05-30 16:12     ` Neil Bothwick

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=49bf44f10905301004v775f019ai8080a9b47776deb5@mail.gmail.com \
    --to=emailgrant@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