From: christophe varoqui <christophe.varoqui@free.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: block allocators and LVMs
Date: Fri, 18 Oct 2002 17:51:47 +0200 [thread overview]
Message-ID: <200210181751.47361.christophe.varoqui@free.fr> (raw)
In-Reply-To: <20021018150337.GA3195@fib011235813.fsnet.co.uk>
On Friday 18 October 2002 17:03, you wrote:
> On Fri, Oct 18, 2002 at 03:04:24PM +0200, christophe.varoqui@free.fr wrote:
> > I realize I didn't pick the right words (from my poor English
> > dictionnary) : I meant an extend remapper rather than a block remapper.
>
> extent remapper.
>
oops, first desillusion :)
>
> What you describe could be very beneficial, especially if you start
> striping the high bandwidth areas. However in no way could this be
> described as 'online FS defragmentation'.
>
I realize the whole concept is different, but could extent remapping alleviate
the need of an *intelligent* FS block allocator, as it ensure the best
statistical-average IO perfs.
I can even imagine an *intelligent* FS block allocator being counter
productive in the case of a heavily fragmented LV (extends out-of-order ...)
because, after all, block allocator seem to take for granted that the device
is linearly mapped over physical.
This whole point fade into mud if the block group object of an extN FS is
mapped over an LVM extent. But even in this case the *simple* allocator would
be best in combination with an extent remapper.
I don't pretend an extent remapper can replace the FS block allocator, but
only *complex* block allocators ... and particularitly those that make the
false assomption that underlying block device is made of linearly and
consecutive physical blocks.
cva
next prev parent reply other threads:[~2002-10-18 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 20:30 christophe varoqui
2002-10-18 11:26 ` Joe Thornber
2002-10-18 13:04 ` christophe.varoqui
2002-10-18 15:03 ` Joe Thornber
2002-10-18 15:51 ` christophe varoqui [this message]
2002-10-18 16:13 ` Joe Thornber
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=200210181751.47361.christophe.varoqui@free.fr \
--to=christophe.varoqui@free.fr \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®