From: Peter Cordes <peter@cordes.ca>
To: Andi Kleen <andi@firstfloor.org>
Cc: xfs@oss.sgi.com
Subject: Re: RAID5/6 writes
Date: Wed, 01 Oct 2008 18:01:36 -0300 [thread overview]
Message-ID: <20081001210136.GM32037@cordes.ca> (raw)
In-Reply-To: <20081001204450.GA25711@one.firstfloor.org>
On Wed, Oct 01, 2008 at 10:44:50PM +0200, Andi Kleen wrote:
> The other problem I can think of is that determing if something is
> free data might need more read IO if the free extent tree is not completely
> cached.
Yeah, I think I mentioned that in my original suggestion. Unless
there are repeated writes with the same hole, it's probably not worth
it to read from disk to figure out if a sector is free. XFS could just
see what it could do with what it already has in memory. This is just
an optimization, so it doesn't have to succeed every time it's possible.
--
#define X(x,y) x##y
Peter Cordes ; e-mail: X(peter@cor , des.ca)
"The gods confound the man who first found out how to distinguish the hours!
Confound him, too, who in this place set up a sundial, to cut and hack
my day so wretchedly into small pieces!" -- Plautus, 200 BC
next prev parent reply other threads:[~2008-10-01 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 17:52 RAID5/6 writes Peter Cordes
2008-10-01 19:36 ` Andi Kleen
2008-10-01 20:13 ` Peter Cordes
2008-10-01 20:44 ` Andi Kleen
2008-10-01 21:01 ` Peter Cordes [this message]
2008-10-02 0:32 ` Dave Chinner
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=20081001210136.GM32037@cordes.ca \
--to=peter@cordes.ca \
--cc=andi@firstfloor.org \
--cc=xfs@oss.sgi.com \
/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