search for: z_streamp

...OF((void)); /* The application can compare zlibVersion and ZLIB_VERSION for consistency. If the first character differs, the library code actually used is not compatible with the zlib.h header file used by the application. @@ -177,7 +177,7 @@ */ /* -extern int ZEXPORT deflateInit OF((z_streamp strm, int level)); +ZEXTERN int ZEXPORT deflateInit OF((z_streamp strm, int level)); Initializes the internal stream state for compression. The fields zalloc, zfree and opaque must be initialized before by the caller. @@ -199,7 +199,7 @@ */ -extern int ZEXPORT deflate OF((z_streamp...

...CONFIG_H -Wall -W -c zlib/deflate.c -o zlib/deflate.o icc: Command line remark: option '-W' not supported zlib/../proto.h(224): remark #310: old-style parameter list (anachronism) void setup_iconv(); ^ zlib/deflate.c(207): remark #310: old-style parameter list (anachronism) z_streamp strm; ^ zlib/deflate.c(208): remark #310: old-style parameter list (anachronism) int level; ^ zlib/deflate.c(209): remark #310: old-style parameter list (anachronism) const char *version; ^ zlib/deflate.c(210): remark #310: old-style parame...

I hacked zstd support into OpenSSH a while ago and just started to clean it up in the recent days. The cleanup includes configuration support among other things that I did not have. During testing I noticed the following differences compared to zlib: - highly interactive shell output (as in refreshed at a _very_ high rate) may result in higher bandwidth compared to zlib. Since zstd is quicker

I added ZSTD support to OpenSSH roughly over a year and I've been playing with it ever since. The nice part is that ZSTD achieves reasonable compression (like zlib) but consumes little CPU so it is unlikely that compression becomes the bottle neck of a transfer. The compression overhead (CPU) is negligible even when uncompressed data is tunneled over the SSH connection (SOCKS proxy, port

.../* compression state is in shared mem, so we can only release it once */ if (do_close && state->compression_buffer) { sshbuf_free(state->compression_buffer); - if (state->compression_out_started) { +#ifdef WITH_ZLIB + if (state->compression_out_started == COMP_ZLIB) { z_streamp stream = &state->compression_out_stream; debug("compress outgoing: " "raw data %llu, compressed %llu, factor %.2f", @@ -619,7 +630,7 @@ ssh_packet_close_internal(struct ssh *ssh, int do_close) if (state->compression_out_failures == 0) deflateEnd(st...

I added ZSTD support to OpenSSH roughly three years ago and I've been playing with it ever since. The nice part is that ZSTD achieves reasonable compression (like zlib) but consumes little CPU so it is unlikely that compression becomes the bottle neck of a transfer. The compression overhead (CPU) is negligible even when uncompressed data is tunneled over the SSH connection (SOCKS proxy, port

Hello, the following patches should get multidisk access working. The syntax accepted is the following: (hdx,y)/path/to/file where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk. the other accepted syntax is using MBR's 32 bits disk signature so for example: (mbr:0x12345678,2)/foo/bar would address

...lib.h --- pristine-linux-2.6.12/include/linux/zlib.h 2005-06-17 21:48:29.000000000 +0200 -+++ linux-2.6.12-xen/include/linux/zlib.h 2006-02-17 00:45:18.227522356 +0100 ++++ linux-2.6.12-xen/include/linux/zlib.h 2006-02-25 00:12:33.768994699 +0100 @@ -506,6 +506,11 @@ extern int zlib_deflateReset (z_streamp stream state was inconsistent (such as zalloc or state being NULL). */ @@ -103112,7 +103115,7 @@ Dynamically update the compression level and compression strategy. The diff -Nurp pristine-linux-2.6.12/kernel/cpu.c linux-2.6.12-xen/kernel/cpu.c --- pristine-linux-2.6.12/kernel/cpu....