From: Jens Axboe <jens.axboe@oracle.com>
To: Tomasz Torcz <tomek@pipebreaker.pl>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: yum upgrade on btrfs very slow
Date: Thu, 1 Oct 2009 11:04:41 +0200 [thread overview]
Message-ID: <20091001090440.GQ14918@kernel.dk> (raw)
In-Reply-To: <20090930194350.GA29166@mother.pipebreaker.pl>
On Wed, Sep 30 2009, Tomasz Torcz wrote:
> I wouldn't expect barriers to work here (reminder, this is PATA drive
> on ICH7 sata controller), but I will test tomorrow with nobarrier.
> Then I probably check his "yum upgrade" under seekwatcher on friday.
Barriers should work fine on that setup. In fact, barriers were first
implemented for PATA back in the day :-)
--
Jens Axboe
next prev parent reply other threads:[~2009-10-01 9:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 12:18 yum upgrade on btrfs very slow Tomasz Torcz
2009-09-28 13:35 ` Chris Mason
2009-09-29 6:18 ` Tomasz Torcz
2009-09-29 13:25 ` Chris Mason
2009-09-30 19:43 ` Tomasz Torcz
2009-10-01 9:01 ` Tomasz Torcz
2009-10-21 9:27 ` Tomasz Torcz
2009-10-26 8:55 ` Chris Mason
2009-10-26 13:35 ` Tomasz Torcz
2009-10-01 9:04 ` Jens Axboe [this message]
2009-10-05 12:09 ` Ric Wheeler
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=20091001090440.GQ14918@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tomek@pipebreaker.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.