Displaying 6 results from an estimated 6 matches for "z_default_compress".
2020 Feb 06
0
[PATCH] Add support for zstd compression
...mp; do_compression_zstd) {
+ snprintf(err_buf, sizeof(err_buf), "Can't mix --compress and zstd\n");
+ return 0;
+ }
+
+ if (do_compression || (def_compress_level != NOT_SPECIFIED && !do_compression_zstd)) {
if (def_compress_level == NOT_SPECIFIED)
def_compress_level = Z_DEFAULT_COMPRESSION;
else if (def_compress_level < Z_DEFAULT_COMPRESSION || def_compress_level > Z_BEST_COMPRESSION) {
@@ -1882,6 +1908,24 @@ int parse_arguments(int *argc_p, const char ***argv_p)
}
#endif
}
+#ifdef HAVE_LIBZSTD
+ if (do_compression_zstd) {
+
+ if (def_compress_level == NOT_SPECIFIE...
2010 Sep 14
2
what is the default value for --compress-level=?
What is the default value for --compress-level=? 6? 9?
The fine manual only mentions:
--compress-level=NUM
Explicitly set the compression level to use (see --compress) instead of letting it default. If NUM is non-zero, the --compress option is implied.
Also, what are allowed values? 1-9? 0-9? Something else?
--
Tomasz Chmielewski
http://wpkg.org
2008 Mar 23
1
[PATCH] allow to change the block size used to handle sparse files
...dex f2d23f6..aaffdc7 100644
--- a/options.c
+++ b/options.c
@@ -73,6 +73,7 @@ int remove_source_files = 0;
int one_file_system = 0;
int protocol_version = PROTOCOL_VERSION;
int sparse_files = 0;
+long sparse_files_block_size = SPARSE_WRITE_SIZE;
int do_compression = 0;
int def_compress_level = Z_DEFAULT_COMPRESSION;
int am_root = 0; /* 0 = normal, 1 = root, 2 = --super, -1 = --fake-super */
@@ -358,6 +359,7 @@ void usage(enum logcode F)
rprintf(F," --fake-super store/recover privileged attrs using xattrs\n");
#endif
rprintf(F," -S, --sparse handle sparse...
2018 Aug 02
3
Default compression level for -compress-debug-info=zlib?
Folks,
I'd like to get expert's opinion on which compression level is suitable for
lld's -compress-debug-section=zlib option, which let the linker compress
.debug_* sections using zlib.
Currently, lld uses compression level 9 which produces the smallest output
in exchange for a longer link time. My question is, is this what people
actually want? We didn't consciously choose
2008 Feb 15
4
Revised flags patch
...because the --no-r option was added at the same time. */
if (xfer_dirs && !recurse && delete_mode && am_sender)
args[ac++] = "--no-r";
+
+ if (preserve_fileflags)
+ args[ac++] = "--fileflags";
if (do_compression && def_compress_level != Z_DEFAULT_COMPRESSION) {
if (asprintf(&arg, "--compress-level=%d", def_compress_level) < 0)
diff -brpu rsync-3.0.0pre9/proto.h rsync-3.0.0pre9-flags/proto.h
--- rsync-3.0.0pre9/proto.h Mon Feb 11 05:12:39 2008
+++ rsync-3.0.0pre9-flags/proto.h Fri Feb 15 19:35:16 2008
@@ -267,6 +267,8 @@ int read_...
2018 Aug 02
3
Default compression level for -compress-debug-info=zlib?
Not really, as well as some sensitivity to the input data overall
performance of the link with compression will depend on how this is
implemented in lld - how is it parallelized? How is it chunked? Is it
effectively pipelined with IO?
Or, I wouldn't feel comfortable being able to make a recommendation to our
end-users on whether to use this option or not based on my existing
extensive