From: Joe Thornber <joe@fib011235813.fsnet.co.uk>
To: christophe.varoqui@free.fr
Cc: linux-kernel@vger.kernel.org
Subject: Re: block allocators and LVMs
Date: Fri, 18 Oct 2002 16:03:37 +0100 [thread overview]
Message-ID: <20021018150337.GA3195@fib011235813.fsnet.co.uk> (raw)
In-Reply-To: <1034946264.3db006d87c82c@imp.free.fr>
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.
> As far as I can see, this task can be done entirely from userland :
>
> o per-extend IO counters exported from kernel-space can be turned into
> a list of extends sorted by activity
>
> o lvdisplay-like tool gives the mapping extend<->physical blocks
>
> o a scheduled job in user-space should be able to massage this info to
> decide where to move low-access-rate-extends to the border of the
> platter and pack high-access-rate-extends together ... all in one run
> that can be scheduled at low activity period (cron defrag way)
>
> The algorithm could be something along the line of :
>
> while top_user_queue_not_empty
> do
> extend = dequeue_lowest_user_extend
> if extend_in_good_spot
> then
> move_extend_to_corner_destination
> find_highest_user_extend_in_bad_spot
> move_this_extend_to_freed_good_spot
> fi
> done
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'.
- Joe
next prev parent reply other threads:[~2002-10-18 14:57 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 [this message]
2002-10-18 15:51 ` christophe varoqui
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=20021018150337.GA3195@fib011235813.fsnet.co.uk \
--to=joe@fib011235813.fsnet.co.uk \
--cc=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®