From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: liblvm Python/C extension (Python Liblvm)
Date: Thu, 20 Jan 2011 16:24:22 +0100 [thread overview]
Message-ID: <4D3853A6.1010209@redhat.com> (raw)
In-Reply-To: <1295527769.24069.31.camel@ljonsson.local>
Dne 20.1.2011 13:49, Lars Sj?str?m napsal(a):
> Hello,
>
> I was missing a proper LVM2 interface to Python so I decided to write
> one my self! I have wrapped all the liblvm C APIs (excluding the new
> APIs committed in Dec). Doc strings are still missing, as well as proper
> setup.py build env, so consider it as work in progress.
>
> This might also be interesting to other projects like Anaconda for
> example.
>
> I would love to get your feedback on it!
>
> Best regards,
> Lars
I can see at least one problem - which needs to be addressed somehow.
Operations like lvremove are currently locking whole executable
to RAM - which is reasonable small (20MB) in case it's just native lvm binary,
but it may get unusable huge when Python steps in the game.
If the lvm2api is going to be used this way - we will need to add
some option which would disable memlocking for this code - and user would
need to enable it probably explicitly.
Zdenek
next prev parent reply other threads:[~2011-01-20 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 12:49 liblvm Python/C extension (Python Liblvm) Lars Sjöström
2011-01-20 15:24 ` Zdenek Kabelac [this message]
2011-01-24 0:11 ` Petr Rockai
2011-01-24 9:58 ` Lars Sjöström
2011-01-24 10:10 ` Zdenek Kabelac
2011-01-24 10:08 ` Zdenek Kabelac
-- strict thread matches above, loose matches on Subject: below --
2012-03-22 7:17 Killian De Volder
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=4D3853A6.1010209@redhat.com \
--to=zkabelac@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.