Displaying 4 results from an estimated 4 matches for "in_block".
Did you mean:
i_block
2020 Jul 10
2
[PATCH nbdkit] New filter: gzip
...;
+}
+
+/* The first thread to call gzip_prepare uncompresses the whole plugin. */
+static int
+do_uncompress (struct nbdkit_next_ops *next_ops, void *nxdata)
+{
+ int64_t compressed_size;
+ z_stream strm;
+ int zerr;
+ const char *tmpdir;
+ size_t len;
+ char *template;
+ CLEANUP_FREE char *in_block = NULL, *out_block = NULL;
+
+ /* This was the same buffer size as used in the old plugin. As far
+ * as I know it was chosen at random.
+ */
+ const size_t block_size = 128 * 1024;
+
+ assert (size == -1);
+
+ /* Get the size of the underlying plugin. */
+ compressed_size = next_ops->...
2020 Jul 10
0
Re: [PATCH nbdkit] New filter: gzip
...ncompresses the whole plugin. */
> +static int
> +do_uncompress (struct nbdkit_next_ops *next_ops, void *nxdata)
> +{
> + int64_t compressed_size;
> + z_stream strm;
> + int zerr;
> + const char *tmpdir;
> + size_t len;
> + char *template;
> + CLEANUP_FREE char *in_block = NULL, *out_block = NULL;
> +
> + /* This was the same buffer size as used in the old plugin. As far
> + * as I know it was chosen at random.
> + */
> + const size_t block_size = 128 * 1024;
> +
> + assert (size == -1);
> +
> + /* Get the size of the underlying...
2019 Nov 12
20
[PATCH hmm v3 00/14] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the others
2019 Oct 28
32
[PATCH v2 00/15] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the others