From: christophe.varoqui@free.fr
To: Joe Thornber <joe@fib011235813.fsnet.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: block allocators and LVMs
Date: Fri, 18 Oct 2002 15:04:24 +0200 (CEST) [thread overview]
Message-ID: <1034946264.3db006d87c82c@imp.free.fr> (raw)
In-Reply-To: <20021018112617.GA1942@fib011235813.fsnet.co.uk>
En réponse à Joe Thornber <joe@fib011235813.fsnet.co.uk>:
> Christophe,
> > the role of intelligent block allocators and/or online FS
> > defragmentation could be replaced by a block remapper in the
> > LVM subsystem.
>
> Crazy idea :)
>
> I think this is best left to the fs to handle, mainly because the
> blocks that the fs deals with are so small. You would end up with
> *huge* remapping tables. Also you would need to spend a lot of time
> collecting the information neccessary calculate the remapping, to do
> it properly you'd need to record an ordering of data acccesses not
> just io counts (ie. so you could build a Markov chain).
>
I realize I didn't pick the right words (from my poor English
dictionnary) : I meant an extend remapper rather than a block 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
This sort of extend reordering is done in some big Storage Arrays like
StorageWorks EVA110 (as far as I know : they are very secretive on the
subject).
next prev parent reply other threads:[~2002-10-18 12:53 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 [this message]
2002-10-18 15:03 ` Joe Thornber
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=1034946264.3db006d87c82c@imp.free.fr \
--to=christophe.varoqui@free.fr \
--cc=joe@fib011235813.fsnet.co.uk \
--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®