From: Dmitry Monakhov <dmonakhov@openvz.org>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Pavel Emelianov <xemul@parallels.com>,
Konstantin Khorenko <khorenko@parallels.com>
Subject: [LSF/MM TOPIC] Use generic FS in virtual environments challenges and solutions
Date: Wed, 29 Jan 2014 18:32:58 +0400 [thread overview]
Message-ID: <87zjmekgdh.fsf@openvz.org> (raw)
Number of virtual environment/container solutions are grow rapidly, here is just
small list of well known names (qemu/kvm, VMware, openvz, LXC, etc)
There are two main challenges any VE solution should overcome:
1) Minimize Guest OS modification (ideally run unmodified binaries)
2) Resource sharing between several VE contexts (mem,cpu,disk)
There are plenty of advanced algorithms for CPU and memory sharing
between VEs. There are no many effective virtualization schemes for
disk at the moment.
OpenVZ project has interesting experience in fs/disk virtualization.
I want to propose three topics about fs/disk virtualization:
1) Effective space allocation scheme aka "Thin provision" [1]
Generic filesystem tries to spawn all it's data across whole disk.
In case of virtual images this result continuous VImage growth
during FS activity even if actual FS disk usage is low.
We have done some research and modified ext4 block allocator
which allow us to reduce VImage swelling effect, I would like to
discuss our finding's.
2) Space reclamation FS/disk shrinking
FS/disk growth is relatively simple operation most disk images and FS allow
online grow [2], but shrink is very heavyweight operation. I would like
to discuss some tricks how to make offline/online shrink less intrusive.
3) Filesystem error detection and correction
At this moment most filesystem may detect internal errors and perform
basic actions(panic,remount_ro) but this reaction is not suitable
for virtual environment because HardwareNode should continue to
operate and fix dedicated VE as soon as possible.
For this purpose it is reasonable to:
A) Implement fs event notification API similar to UEVENTs for devices or
quota event API. I would like to discuss this API.
B) Reduce fsck time. Theodore Tso have announced initiative to implement
ffck for ext4 [3]. I want to discuss perspectives of design and
implementation online fsck for ext4.
Footnotes:
[1] http://en.wikipedia.org/wiki/Thin_provisioning
[2] http://openvz.org/Ploop
[3] http://marc.info/?l=linux-ext4&m=138661211607779&w=2
next reply other threads:[~2014-01-29 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 14:32 Dmitry Monakhov [this message]
2014-01-29 15:37 ` [Lsf-pc] [LSF/MM TOPIC] Use generic FS in virtual environments challenges and solutions Jan Kara
2014-01-30 7:51 ` Dmitry Monakhov
2014-01-30 10:05 ` Jan Kara
2014-01-30 13:41 ` Dmitry Monakhov
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=87zjmekgdh.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=khorenko@parallels.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=xemul@parallels.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 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.