Displaying 3 results from an estimated 3 matches for "type_flag".
Did you mean:
type_flags
2019 Mar 19
0
[PATCH nbdkit 3/9] server: Implement Block Status requests to read allocation status.
...p = rv;
+
+ (*rp)++;
+ return 0;
+}
+
+struct copy_extents_data {
+ size_t i;
+ struct block_descriptor *blocks;
+ size_t nr_blocks;
+};
+
+static int
+copy_extents (uint64_t offset, uint64_t length, uint32_t type,
+ void *dv)
+{
+ struct copy_extents_data *data = dv;
+ uint32_t type_flags;
+
+ assert (data->i < data->nr_blocks);
+
+ /* Because the original request is limited to a 32 bit count, length
+ * can never be > 32 bits in size.
+ */
+ assert (length <= UINT32_MAX);
+
+ /* Convert NBDKIT_EXTENT_* flags to NBD_STATE_* flags. However
+ * since these a...
2010 Oct 06
0
multiple record types from a single file efficiently?
...arse the line
according to the flag in character position given by flag_pos....
thoughts?
loadhierarchy <- function(indata,dd_by_type,flag_pos) {
# read indata line by line and add each row based on its record type
# we'll grab the line, compare the character in col position flag_pos to
type_flag (column 3 in dd_by_type) and
# rbind to the data with the right formatting
i <- 1
width <- max(sum(unlist(dd_by_type[1:dim(dd_by_type)[1],3])))
#for (i in 1:dim(dd_by_type)[1]) {
#assign(paste("con_",i,sep=""),file(paste(file.path(indata),"_",i,".csv"...
2019 Mar 19
15
[PATCH nbdkit 0/9] [mainly for discussion and early review] Implement extents.
I want to post this but mainly for discussion and early review. It's
not safe for these patches to all go upstream yet (because not all
filters have been checked/adjusted), but if any patches were to go
upstream then probably 1 & 2 only are safe.
File, VDDK, memory and data plugins all work, although I have only
done minimal testing on them.
The current tests, such as they are, all