Displaying 6 results from an estimated 6 matches for "recv_request".
Did you mean:
ecp_request
2007 Apr 01
2
strange behavior after switching to DRb server
...r/local/lib/ruby/1.8/drb/drb.rb:582:in
`load''
(druby://localhost:9010) /usr/local/lib/ruby/1.8/thread.rb:33:in
`exclusive''
(druby://localhost:9010) /usr/local/lib/ruby/1.8/drb/drb.rb:578:in
`load''
(druby://localhost:9010) /usr/local/lib/ruby/1.8/drb/drb.rb:616:in
`recv_request''
(druby://localhost:9010) /usr/local/lib/ruby/1.8/drb/drb.rb:615:in
`recv_request''
(druby://localhost:9010) /usr/local/lib/ruby/1.8/drb/drb.rb:908:in
`recv_request''
(druby://localhost:9010) /usr/local/lib/ruby/1.8/drb/drb.rb:1527:in
`init_with_client''
(drub...
2018 Jan 19
2
Re: [nbdkit PATCH v2 13/13] RFC: plugins: Add callbacks for FUA semantics
...and build has been changed to be in line with our other
internal projects.
I have uploaded the entire cbdkit source to our github at
https://github.com/dev-cloudbd/cbdkit
The relevant files are
include/cbdkit-plugin.h
src/connections.c
src/plugins.c
Specifically, the connections.c functions
recv_request
send_reply
and the plugins.c functions
plugin_pread
plugin_pwrite
cbdkit_async_reply
cbdkit_async_reply_read
cbdkit_async_reply_error
On Fri, Jan 19, 2018 at 12:05 PM, Eric Blake <eblake@redhat.com> wrote:
> On 01/19/2018 10:56 AM, Shaun McDowell wrote:
>
> > Limitation:...
2006 Nov 01
1
strange issue with backgroundrb behind apache/lighttpd
...t:42531) /usr/lib/ruby/1.8/drb/drb.rb:375:in `to_obj''
(druby://localhost:42531) /usr/lib/ruby/1.8/drb/drb.rb:1402:in `to_obj''
(druby://localhost:42531) /usr/lib/ruby/1.8/drb/drb.rb:1704:in `to_obj''
(druby://localhost:42531) /usr/lib/ruby/1.8/drb/drb.rb:613:in `recv_request''
(druby://localhost:42531) /usr/lib/ruby/1.8/drb/drb.rb:911:in `recv_request''
(druby://localhost:42531) /usr/lib/ruby/1.8/drb/drb.rb:1530:in `init_with_cl
ient''
(druby://localhost:42531) /usr/lib/ruby/1.8/drb/drb.rb:1542:in `setup_messag
e''
(druby...
2017 Feb 20
1
Re: Fwd: nbdkit async
...over the
network. While our plugin waits for the read or write data we don't block
in a thread we handle other requests that are ready).
The current nbdkit server design requires a thread per request in progress
because it is built around a synchronous callback to the plugin layer and
the main recv_request_send_reply loop holds the only copy of the request
handle that is needed to make the reply.
A more flexible design would be the recv_request_send_reply loop is instead
split into a recv_request loop and a send_reply func. The recv_request loop
forwards the request handle to the handle_request call...
2017 Feb 19
2
Fwd: nbdkit async
----- Forwarded message -----
Date: Sat, 18 Feb 2017 22:21:19 -0500
Subject: nbdkit async
Hello,
Hope this is the right person to contact regarding nbdkit design.
I have a high latency massively parallel device that I am currently
implementing as an nbdkit plugin in c++ and have run into some design
limitations due to the synchronous callback interface nbdkit requires.
Nbdkit is currently
2018 Jan 19
2
Re: [nbdkit PATCH v2 13/13] RFC: plugins: Add callbacks for FUA semantics
Hi,
We've been using a modified nbdkit (ours is cbdkit internally) for about
half a year now and since you guys appear to be working on a next version
of the API I wanted to go over some of the limitations we hit with nbdkit
that we think others may also hit for consideration into the batch of
changes you are making to the api.
About Us: Our primary use for nbdkit is to facilitate a disk