search for: l430

> * Calling getBaseObject() on a GlobalIFunc returns its resolver function. I still don't understand how it can happen looking to the code ( https://github.com/llvm/llvm-project/blob/master/llvm/lib/IR/Globals.cpp#L430). I believe it should return nullptr (the same as if you call it from GlobalAlias that refers to GlobalIFunc). I don't have a strong opinion here because deriving GlobalIFunc from GlobalObject does make some sense. At the same time from implementation point of view there were lots of similarit...

Thanks Pino for quick response. Actually I use the libguestfs APIs in C++ program. Following your idea, I think I should try guestfs_set_network for this. Please correct me if I have any misunderstanding. Thanks, Allen 2016-07-12 16:38 GMT+08:00 Pino Toscano <ptoscano@redhat.com>: > Hi, > > On Tuesday, 12 July 2016 16:30:17 CEST Baochuan Wu wrote: > > I mounted virtual

...on CentOS 7, I installed > libguestfs into the CentOS 6.4. After installing, I reboot CentOS 6.4 but I > cannot log into it anymore. You will need to relabel the filesystem after installing packages, see: https://github.com/libguestfs/libguestfs/blob/master/customize/customize_run.ml#L415-L430 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html

...ibguestfs into the CentOS 6.4. After installing, I reboot CentOS 6.4 > but I > > cannot log into it anymore. > > You will need to relabel the filesystem after installing packages, see: > > > https://github.com/libguestfs/libguestfs/blob/master/customize/customize_run.ml#L415-L430 > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat > http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-builder quickly builds VMs from scratch > http://libguestfs.org/virt-builder.1.html >

...AY, at the expense of potentially more network traffic overhead. One more code search, and I find that we use TCP_NODELAY in all of: qemu client: https://gitlab.com/qemu-project/qemu/-/blob/master/nbd/client-connection.c#L143 nbdkit: https://gitlab.com/nbdkit/nbdkit/-/blob/master/server/sockets.c#L430 libnbd: https://gitlab.com/nbdkit/libnbd/-/blob/master/generator/states-connect.c#L41 so I think we _should_ be calling qio_channel_set_delay(false) for qemu-nbd as well. That doesn't negate your patch, but rather argues that we can go for even better performance with TCP_NODELAY also turned...

http://git.annexia.org/?p=libguestfs.git;a=blob;f=daemon/debug.c;h=cd3e8a5f0294a910782b38552d2b0757869f862c;hb=HEAD#l430 Coverity complains about the error path from posix_memalign (lines 477-482) saying that 'buf' will be leaked. However my reading of the posix_memalign man page is that if the return value from posix_memalign != 0 then 'buf' would not have been allocated. Rich. -- Richard Jones,...

On Fri, Mar 24, 2023 at 11:47:20AM +0100, Florian Westphal wrote: > qemu-nbd doesn't set TCP_NODELAY on the tcp socket. > > Kernel waits for more data and avoids transmission of small packets. > Without TLS this is barely noticeable, but with TLS this really shows. > > Booting a VM via qemu-nbd on localhost (with tls) takes more than > 2 minutes on my system. tcpdump

I was working on https://reviews.llvm.org/D81911 to try and fix https://bugs.llvm.org/show_bug.cgi?id=46340 . Through the review process we happened upon a design limitation or perhaps a potential mis-modelling of GlobalIFunc in the IR object hierarchy, which leads to some problems in LTO flows. To summarize, as it currently stands (and in the hopes of faithfully representing the conclusions of

...nd a default N value. Both Abseil and Folly have a SmallVector equivalent, Abseil does not have a default: https://github.com/abseil/abseil-cpp/blob/master/absl/container/inlined_vector.h#L69-L71 Folly has a default hard-coded to 1: https://github.com/facebook/folly/blob/master/folly/small_vector.h#L430 Folly has also another class, FBVector, which is really an alternative to std::vector with a different memory management strategy (growth factor, etc.). I don't think Abseil has anything else. Do you have other ideas of related work to look for? > > >> I wouldn't entirely ob...

...d Folly have a SmallVector equivalent, Abseil does not have >> a default: >> https://github.com/abseil/abseil-cpp/blob/master/absl/container/inlined_vector.h#L69-L71 >> Folly has a default hard-coded to 1: >> https://github.com/facebook/folly/blob/master/folly/small_vector.h#L430 >> Folly has also another class, FBVector, which is really an alternative to >> std::vector with a different memory management strategy (growth factor, >> etc.). I don't think Abseil has anything else. >> >> Do you have other ideas of related work to look for? >...

...; Both Abseil and Folly have a SmallVector equivalent, Abseil does not have > a default: > https://github.com/abseil/abseil-cpp/blob/master/absl/container/inlined_vector.h#L69-L71 > Folly has a default hard-coded to 1: > https://github.com/facebook/folly/blob/master/folly/small_vector.h#L430 > Folly has also another class, FBVector, which is really an alternative to > std::vector with a different memory management strategy (growth factor, > etc.). I don't think Abseil has anything else. > > Do you have other ideas of related work to look for? > Actually, the reas...

On Mon, Nov 16, 2020 at 2:12 PM David Blaikie <dblaikie at gmail.com> wrote: > On Mon, Nov 16, 2020 at 1:55 PM Mehdi AMINI <joker.eph at gmail.com> wrote: > > On Mon, Nov 16, 2020 at 12:55 PM David Blaikie <dblaikie at gmail.com> > wrote: > >> > >> I will say I'm not a huge fan of adding even more names for things in > >> this fairly