On Tuesday, 2021-03-23 at 15:40:24 -04, Michael S. Tsirkin wrote:
> On Tue, Mar 23, 2021 at 05:40:36PM +, Daniel P. Berrangé wrote:
>> On Tue, Mar 23, 2021 at 05:54:47PM +0100, Igor Mammedov wrote:
>> > Let me hijack this thread for beyond this case scope.
>> >
>> > I agree that for this
On Wed, Apr 08, 2009 at 12:09:06PM +0100, Daniel P. Berrange wrote:
On Wed, Apr 08, 2009 at 01:06:48PM +0200, Maximilian Wilhelm wrote:
Anno domini 2009 Daniel P. Berrange scripsit:
[...]
In the (nearish) future NICs will start appearing with SR-IOV
capabilities.
This gives you
There's an assumption that XenEnterprise actually uses xend. Is that
the case? ('ps' might tell you)
dme.
--
David Edmondson, Sun Microsystems, http://dme.org
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
On Wed, Mar 21, 2007 at 04:38:00PM +0100, Jim Meyering wrote:
I interpret wrappers, above, to mean more than just a calloc-like wrapper.
A malloc (not calloc, of course) wrapper that always initializes can
mask what would have otherwise been a used-uninitialised error, and what
would still
On Thu, Mar 22, 2007 at 11:22:21AM +, Richard W.M. Jones wrote:
Secondly there is an API of sorts for lvm2. I think Alasdair called it
libcmd, but maybe I got that wrong because Google doesn't seem to turn
up anything. In any case, all it is is a wrapper around the command
line tools,
On Tue, Mar 20, 2007 at 04:00:21PM +, Daniel P. Berrange wrote:
On this subject, does ZFS come with any library API for doing all
the volume pool management tasks, or is it all just a set of command
line tools as we'd get with LVM ?
There's no Committed C API for ZFS management tasks
On Wed, Mar 21, 2007 at 09:39:15AM -0400, Daniel Veillard wrote:
Well, one of the things I do in my wrapper is initilize to -1 all newly
allocated bytes, allows to pinpoint relatively easilly when you assumed zeroed
memory which was not, while not paying for the initialization when not
