public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Maninder Singh <maninder1.s@samsung.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	minchan@kernel.org, ngupta@vflare.org,
	sergey.senozhatsky.work@gmail.com, keescook@chromium.org,
	anton@enomsg.org, ccross@android.com, tony.luck@intel.com,
	akpm@linux-foundation.org, colin.king@canonical.com,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	pankaj.m@samsung.com, a.sahrawat@samsung.com,
	v.narang@samsung.com
Subject: Re: [PATCH 0/1] cover-letter/lz4: Implement lz4 with dynamic offset length.
Date: Wed, 21 Mar 2018 15:41:28 +0900	[thread overview]
Message-ID: <20180321064128.GA468@jagdpanzerIV> (raw)
In-Reply-To: <1521607242-3968-1-git-send-email-maninder1.s@samsung.com>

On (03/21/18 10:10), Maninder Singh wrote:
> (Added cover letter to avoid much text in patch description)
> 
> LZ4 specification defines 2 byte offset length for 64 KB data.
> But in case of ZRAM we compress data per page and in most of
> architecture PAGE_SIZE is 4KB. So we can decide offset length based
> on actual offset value. For this we can reserve 1 bit to decide offset
> length (1 byte or 2 byte). 2 byte required only if ofsset is greater than 127,
> else 1 byte is enough.

So what happens if I compress the data on a system with no dyn
offset and then send it over the network to a machine which has
dyn offset? Or, say, I have a USB stick with a compression enabled
FS, store files on a dyn offset enabled PC and then mount that USB
stick on a machine with no dyn offset support. And vice versa.

	-ss

  parent reply	other threads:[~2018-03-21  6:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180321044137epcas5p221e7ee4a0b7464eaa00dad8320f0251d@epcas5p2.samsung.com>
2018-03-21  4:40 ` [PATCH 0/1] cover-letter/lz4: Implement lz4 with dynamic offset length Maninder Singh
2018-03-21  4:40   ` [PATCH 1/1] lz4: " Maninder Singh
2018-03-21  7:49     ` Sergey Senozhatsky
2018-04-02  5:51       ` Maninder Singh
2018-04-03 12:26         ` Sergey Senozhatsky
2018-04-03 13:43           ` Vaneet Narang
2018-04-04  1:40             ` Sergey Senozhatsky
2018-03-21 19:59     ` Nick Terrell
2018-03-22  4:28       ` Maninder Singh
2018-03-23 13:21         ` Vaneet Narang
2018-03-22 23:09     ` kbuild test robot
2018-03-22 23:32     ` kbuild test robot
2018-03-21  6:41   ` Sergey Senozhatsky [this message]
2018-04-02  6:03     ` [PATCH 0/1] cover-letter/lz4: " Maninder Singh
2018-03-21  8:26   ` Sergey Senozhatsky
2018-03-21 19:56     ` Nick Terrell
2018-03-22  2:43       ` Sergey Senozhatsky
2018-03-23 13:43       ` Vaneet Narang
     [not found]     ` <CGME20180321044137epcas5p221e7ee4a0b7464eaa00dad8320f0251d@epcms5p6>
     [not found]       ` <20180329102046epcms5p8ecc9532b03bab4f47cbdbb2507171b86@epcms5p8>
2018-03-29 10:26         ` Maninder Singh
2018-03-30  5:41           ` Sergey Senozhatsky
2018-04-16 10:21           ` Maninder Singh
2018-04-16 19:34             ` Yann Collet
2018-04-16 20:01               ` Eric Biggers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180321064128.GA468@jagdpanzerIV \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=a.sahrawat@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=colin.king@canonical.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=keescook@chromium.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maninder1.s@samsung.com \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=pankaj.m@samsung.com \
    --cc=tony.luck@intel.com \
    --cc=v.narang@samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox