Displaying 4 results from an estimated 4 matches for "cbdkit_thread_model_async".
2018 Jan 19
2
Re: [nbdkit PATCH v2 13/13] RFC: plugins: Add callbacks for FUA semantics
...gigabit networking on < 100MB of memory in
the driver with this approach.
Here are some of what our function prototypes look like that support an
asynchronous nbdkit model
#define CBDKIT_THREAD_MODEL_SERIALIZE_REQUESTS 2
#define CBDKIT_THREAD_MODEL_PARALLEL 3
#define CBDKIT_THREAD_MODEL_ASYNC 4
struct cbdkit_plugin {
...
int (*pread) (void *handle, void *buf, uint32_t count, uint64_t offset);
int (*pwrite) (void *handle, const void *buf, uint32_t count, uint64_t
offset);
int (*flush) (void *handle);
int (*trim) (void *handle, uint32_t count, uint64_t offse...
2018 Jan 19
0
Re: [nbdkit PATCH v2 13/13] RFC: plugins: Add callbacks for FUA semantics
...ogether and possible
with fewer threads.
>
> Here are some of what our function prototypes look like that support an
> asynchronous nbdkit model
>
> #define CBDKIT_THREAD_MODEL_SERIALIZE_REQUESTS 2
> #define CBDKIT_THREAD_MODEL_PARALLEL 3
> #define CBDKIT_THREAD_MODEL_ASYNC 4
>
> struct cbdkit_plugin {
> ...
> int (*pread) (void *handle, void *buf, uint32_t count, uint64_t offset);
> int (*pwrite) (void *handle, const void *buf, uint32_t count, uint64_t
> offset);
> int (*flush) (void *handle);
> int (*trim) (void...
2018 Jan 19
2
Re: [nbdkit PATCH v2 13/13] RFC: plugins: Add callbacks for FUA semantics
...ds.
>
> >
> > Here are some of what our function prototypes look like that support an
> > asynchronous nbdkit model
> >
> > #define CBDKIT_THREAD_MODEL_SERIALIZE_REQUESTS 2
> > #define CBDKIT_THREAD_MODEL_PARALLEL 3
> > #define CBDKIT_THREAD_MODEL_ASYNC 4
> >
> > struct cbdkit_plugin {
> > ...
> > int (*pread) (void *handle, void *buf, uint32_t count, uint64_t
> offset);
> > int (*pwrite) (void *handle, const void *buf, uint32_t count, uint64_t
> > offset);
> > int (*flush) (...
2018 Jan 19
16
[nbdkit PATCH v2 00/13] Add filters + FUA support to nbdkit
A combination of the work that both Rich and I have been doing
lately, where filters use only the new API with flags on every
command that the client can send over the wire (we can then
add support for more flags in nbdkit without having to add new
callbacks, as NBD adds more flags upstream).
Eric Blake (4):
protocol: Split flags from cmd field in requests
backend: Pass flags argument through