search for: asychron

...iff --git a/docs/libnbd.pod b/docs/libnbd.pod > > index 72f74053..433479e6 100644 > > --- a/docs/libnbd.pod > > +++ b/docs/libnbd.pod > > @@ -904,9 +904,12 @@ same nbd object, as it would cause deadlock. > > =head2 Completion callbacks > > > > All of the asychronous commands have an optional completion callback > > -function that is used right before the command is marked complete, > > -after any mid-command callbacks have finished, and before any free > > -functions. > > +function that is used if the asynchronous command succeeded,...

...synchronously, meaning that we would issue a request for each data >block from the nbdkit server (which would in turn synchronously >request the data from VMware) and wait until nbdkit replies before >continuing. > >This converts the inner loop so it issues as many pread requests >asychronously to nbdkit as the server can handle (any extra are queued >in nbd_handle). The server will answer these in parallel and possibly >out of order. > >This results in somewhat better throughput (for me: 13 minutes down to >5 minutes for an "initial" run). Although unfortu...

...d.pod b/docs/libnbd.pod >>> index 72f74053..433479e6 100644 >>> --- a/docs/libnbd.pod >>> +++ b/docs/libnbd.pod >>> @@ -904,9 +904,12 @@ same nbd object, as it would cause deadlock. >>> =head2 Completion callbacks >>> >>> All of the asychronous commands have an optional completion callback >>> -function that is used right before the command is marked complete, >>> -after any mid-command callbacks have finished, and before any free >>> -functions. >>> +function that is used if the asynchronous command...

...segfaulted on three different boxes. Backtraces are attached to help track this down. http://bugs.digium.com/view.php?id=6027 - This is related to the bug above and has a different patch that might be relevant. http://bugs.digium.com/view.php?id=5374 - This is a patch that allows for the asychronous generation of outgoing frames. Very cool. Needs a decision by the Core Developers (Read Kram / KPFleming). BJ has been keeping this in synch w/ Trunk in his own branch. http://bugs.digium.com/view.php?id=5090 - T.38 Support anyone? http://bugs.digium.com/view.php?id=5574 - A nift...

...ue nbd.pread() requests synchronously, meaning that we would issue a request for each data block from the nbdkit server (which would in turn synchronously request the data from VMware) and wait until nbdkit replies before continuing. This converts the inner loop so it issues as many pread requests asychronously to nbdkit as the server can handle (any extra are queued in nbd_handle). The server will answer these in parallel and possibly out of order. This results in somewhat better throughput (for me: 13 minutes down to 5 minutes for an "initial" run). Although unfortunately we are still...

This is based on top of: https://github.com/nertpinx/v2v-conversion-host/commit/0bb2efdcacd975a2cae7380080991ac7fc238d2b The first 4 patches are fairly uncontroversial miscellaneous cleanups. Patch 5 is the interesting one. (Note it doesn't quite work yet, so it's for discussion only.) Patch 5 converts the inner loop to use asynchronous libnbd calls. performance improves quite a bit for

Hi, We needed a vorbis decoder that operated differently from the approach taken libvorbisfile. So I sat down, looked through the docs, and the sample decoder that come with libvorbis and wrote our own. Since I couldn't find any docs for the API for libvorbis itself, I've written some. It details all the steps you need to go through to write a _basic_ reusable decoder library using

...would issue a request for each data > >block from the nbdkit server (which would in turn synchronously > >request the data from VMware) and wait until nbdkit replies before > >continuing. > > > >This converts the inner loop so it issues as many pread requests > >asychronously to nbdkit as the server can handle (any extra are queued > >in nbd_handle). The server will answer these in parallel and possibly > >out of order. > > > >This results in somewhat better throughput (for me: 13 minutes down to > >5 minutes for an "initial&quot...

hi, can''t find any good tutorial or advice to deal with the creation of a new record and it''s associated objects within the same page. do i have to use ajax just to add custom form fields that will be handled by the controller for associated objects creation.? do i have to use ajax to add associated objects to the unsaved but allready in session parent object? what''s

hi all, curious about your input on this latest design experience i''ve had with camping. none of that developing a traditional html ui, a ruby backend, and ajax-ifying the application after being built. - i started straight off with a camping-based json api (for the model). - next step was writing the controller in pure js - no dom interactions here. - then finishing off with a view

This is my proposal for fixing the documentation to match practice (namely, that completion.callback is not invoked in the cases where the aio call itself reports errors); we could instead try to go the other direction and tweak the generator to guarantee that both completion.callback and completion.free are reached no matter what, but that felt more invasive to me. Eric Blake (2): api: Tighten

Background ---------- A complaint I'm hearing is that some tools which take a long time to run (virt-resize in particular) need to have progress bars to indicate how long they are expected to run. This is also a basic usability principle, see for example this paper: http://www.chrisharrison.net/projects/progressbars/ProgBarHarrison.pdf If you look at how virt-resize is implemented, the bulk

This patch series is separated from the previous "Virtio-balloon Enhancement" series. The new feature, VIRTIO_BALLOON_F_FREE_PAGE_HINT, implemented by this series enables the virtio-balloon driver to report hints of guest free pages to the host. It can be used to accelerate live migration of VMs. Here is an introduction of this usage: Live migration needs to transfer the VM's

...e aborted with a timeout error. A connection which is currently being used to execute a query will be considered dead if no forward progress of any kind has happened for 20 seconds (also arbitrary). If this happens (or if some kind of I/O error occurs), the existing connection will be closed and an asychronous connect on a newly created one will be started. Assuming the lifetime of the query isn't yet over, it will either be started again on another available connection or pushed back onto the front of the query queue, causing it to be started as soon as a connection becomes available. Attemtps to...