From: Zdenek Kabelac <zkabelac@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Eli Malul <eli.malul@kaminario.com>
Subject: Re: Huge memory allocation
Date: Thu, 03 Mar 2011 09:41:47 +0100 [thread overview]
Message-ID: <4D6F544B.409@redhat.com> (raw)
In-Reply-To: <E04C10E329E0CD40816C9C17AE53BBD301863EB0@kit001.kaminario.local>
Dne 3.3.2011 09:05, Eli Malul napsal(a):
> I am expecting to have lots of (up to million) scattered extents across
> some volumes which I am required to mirror.
> Since mirror mapped device with a table that large consume unbearable
> amount of memory (e.g. for 10,000 extents I saw about 6 Giga of memory
> allocated by the device-mapper) I am going to create two linear devices
> which maps these extents and mirror them.
>
> In addition, I am required to preserve the original extent's offsets
> since they are an existing user data used by DB applications.
> To achieve that I will create another linear device to simulate the
> original extent's offsets which shall be mapped to the created mirrored
> device so, the client will continue to read and write the same offsets.
>
Aren't you trying to reinvent dm-replicator target ?
(available as an extra kernel patch)
Maybe you should first describe exactly what are you trying to achieve.
I'd guess there would be better ways to achieve that goal.
Updating kernel tables is expensive operation - especially if you plan to have
its size in the range of multiple megabytes - so it looks like wrong plan...
Zdenek
next prev parent reply other threads:[~2011-03-03 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 13:04 Huge memory allocation Eli Malul
2011-03-01 13:46 ` Alasdair G Kergon
2011-03-03 8:05 ` Eli Malul
2011-03-03 8:41 ` Zdenek Kabelac [this message]
2011-03-03 8:58 ` Eli Malul
2011-03-03 10:00 ` Zdenek Kabelac
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=4D6F544B.409@redhat.com \
--to=zkabelac@redhat.com \
--cc=dm-devel@redhat.com \
--cc=eli.malul@kaminario.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