From: Petr Rockai <prockai@redhat.com>
To: lvm-devel@redhat.com
Subject: [DRAFT PATCH] lvmcache and lvmetad
Date: Mon, 24 Oct 2011 16:17:17 +0200 [thread overview]
Message-ID: <8739eiiidu.fsf@aldalome.int.mornfall.net.> (raw)
Hi,
I have been working on isolating lvmcache code from the rest of the
codebase. I am making progress slowly, since this is very tedious and
very error-prone. A lot of code is copied out around the code base and
cache internals are manipulated all over the place. I am attaching my
current state of the matters, which do not yet compile. When you expose
the internal structures, you can get things to compile though and pass
the tests as well. I will continue drilling down while trying to avoid
any new bugs.
The plan is to, when the lvmcache is finally walled off, to create a new
implementation (of the APIs) that only does the bare minimum to get LVM
going and passing the testsuite. The following step would then be to
factor this functionality out of lvmcache altogether, as far as that
turns out to be possible. After that is done, finally, I can resume work
on integrating lvmetad, which has been so far blocked out by lvmcache
mis-design. In the meantime, I'll try to integrate some lvmetad tests
into the suite (the daemon can be tested even without full LVM support).
Yours,
Petr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lvmcache.diff
Type: text/x-diff
Size: 39299 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20111024/8036749b/attachment.bin>
-------------- next part --------------
--
id' Ash = Ash; id' Dust = Dust; id' _ = undefined
next reply other threads:[~2011-10-24 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 14:17 Petr Rockai [this message]
2011-11-07 15:48 ` [PATCH] lvmcache and lvmetad, part 1: isolation of lvmcache Petr Rockai
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=8739eiiidu.fsf@aldalome.int.mornfall.net. \
--to=prockai@redhat.com \
--cc=lvm-devel@redhat.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.