Displaying 3 results from an estimated 3 matches for "writeflags".
Did you mean:
write_flags
2019 Aug 13
0
[nbdkit PATCH 2/2] nozero: More efficient FUA handling
...nd binary forms, with or without
* modification, are permitted provided that the following conditions are
@@ -102,12 +102,22 @@ nozero_zero (struct nbdkit_next_ops *next_ops, void *nxdata,
void *handle, uint32_t count, uint64_t offs, uint32_t flags,
int *err)
{
+ int writeflags = 0;
+ bool need_flush = false;
+
assert (zeromode != NONE);
flags &= ~NBDKIT_FLAG_MAY_TRIM;
if (zeromode == NOTRIM)
return next_ops->zero (nxdata, count, offs, flags, err);
+ if (flags & NBDKIT_FLAG_FUA) {
+ if (next_ops->can_fua (nxdata) == NBDKIT_FUA_EMULATE)
+...
2019 Aug 13
3
[nbdkit PATCH 0/2] more fast zero prep
Another couple things I noticed that are worth improving, but aren't
strictly related to implementing fast zero support.
Eric Blake (2):
server: Assert sane error responses
nozero: More efficient FUA handling
filters/nozero/nozero.c | 17 +++++++++++--
server/filters.c | 56 +++++++++++++++++++++++++++++++++--------
server/protocol.c | 32 +++++++++++++++++------
3 files
2007 Apr 13
2
R on Solaris 10 x64
Hi R Developers,
Greg is helping me with debugging R on Solaris 10 x64. Please let us
know if you have any thoughts or tips that can help us debug this.
Thanks,
David
************
Using default transfer plist
in vector_io: permuting
About to write
*** caught segfault ***
address e8554000, cause 'memory not mapped'
Traceback:
1: .External("do_hdf5save", call,