linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: cwillu <cwillu@cwillu.com>
To: Harald Glatt <mail@hachre.de>
Cc: Leonidas Spyropoulos <artafinde@gmail.com>,
	Martin Steigerwald <Martin@lichtvoll.de>,
	Duncan <1i5t5.duncan@cox.net>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Recommended settings for SSD
Date: Sun, 26 May 2013 11:06:22 -0600	[thread overview]
Message-ID: <CAE5mzvgVdmckePvkdUomd2fUWFxkdgoQRLgtTWjCQQQ9jYUbEg@mail.gmail.com> (raw)
In-Reply-To: <CAFWF=akw41MyFLAasCx90M6MU7dBU8DVEMDzRMsiEwNMFZMkOA@mail.gmail.com>

On Sun, May 26, 2013 at 9:16 AM, Harald Glatt <mail@hachre.de> wrote:
> I don't know a better way to check than doing df -h before and
> after... If you use space_cache you have to clear_cache though to make
> the numbers be current for sure each time before looking at df.

Not sure what you're thinking of; space_cache is just a mount-time
optimization, storing and loading a memory structure to disk so that
it doesn't have to be regenerated.

As I understand it, if it's ever wrong, it's a serious bug.

  reply	other threads:[~2013-05-26 17:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 20:06 Recommended settings for SSD Leonidas Spyropoulos
2013-05-24 20:07 ` cwillu
2013-05-24 22:38   ` Leonidas Spyropoulos
2013-05-25  3:58     ` Duncan
2013-05-25  8:21       ` Leonidas Spyropoulos
2013-05-25 10:14         ` Russell Coker
2013-05-25 12:13       ` Martin Steigerwald
2013-05-25 13:30         ` Duncan
2013-05-25 22:29         ` Leonidas Spyropoulos
2013-05-25 22:33           ` Harald Glatt
2013-05-26 10:00             ` Leonidas Spyropoulos
2013-05-26 15:16               ` Harald Glatt
2013-05-26 17:06                 ` cwillu [this message]
2013-05-25 22:49           ` Martin Steigerwald
2013-05-25 22:46         ` Martin Steigerwald

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=CAE5mzvgVdmckePvkdUomd2fUWFxkdgoQRLgtTWjCQQQ9jYUbEg@mail.gmail.com \
    --to=cwillu@cwillu.com \
    --cc=1i5t5.duncan@cox.net \
    --cc=Martin@lichtvoll.de \
    --cc=artafinde@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mail@hachre.de \
    /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;
as well as URLs for NNTP newsgroup(s).