linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: Enzo Matsumiya <ematsumiya@suse.de>
Cc: Jan Kara <jack@suse.cz>,
	lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-cifs@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] Over-the-wire data compression
Date: Mon, 18 Mar 2024 21:59:55 +1100	[thread overview]
Message-ID: <20240318215955.47e408bf@echidna> (raw)
In-Reply-To: <20240315122231.ktyx3ebd5mulo5or@quack3>

Hi Enzo,

...
> On Thu 14-03-24 15:14:49, Enzo Matsumiya wrote:
> > Hello,
> > 
> > Having implemented data compression for SMB2 messages in cifs.ko, I'd
> > like to attend LSF/MM to discuss:
> > 
> > - implementation decisions, both in the protocol level and in the
> >   compression algorithms; e.g. performance improvements, what could,
> >   if possible/wanted, turn into a lib/ module, etc
> > 
> > - compression algorithms in general; talk about algorithms to determine
> >   if/how compressible a blob of data is
> >     * several such algorithms already exist and are used by on-disk
> >       compression tools, but for over-the-wire compression maybe the
> >       fastest one with good (not great nor best) predictability
> >       could work?

Ideally there could be some overlap between on-disk and over-the-wire
compression algorithm support. That could allow optimally aligned /
sized IOs to avoid unnecessary compression / decompression cycles on an
SMB server / client if the underlying filesystem supports encoded I/O
via e.g. BTRFS_IOC_ENCODED_READ/WRITE.

IIUC, we currently have:
SMB: LZ77, LZ77+Huffman (DEFLATE?), LZNT1, LZ4
Btrfs: zlib/DEFLATE, LZO, Zstd
Bcachefs: zlib/DEFLATE, LZ4, Zstd. Currently no encoded I/O support.

Cheers, David

  reply	other threads:[~2024-03-18 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <rnx34bfst5gyomkwooq2pvkxsjw5mrx5vxszhz7m4hy54yuma5@huwvwzgvrrru>
2024-03-15 12:22 ` [Lsf-pc] [LSF/MM ATTEND] Over-the-wire data compression Jan Kara
2024-03-18 10:59   ` David Disseldorp [this message]
2024-03-22 21:23     ` Enzo Matsumiya
2024-03-25 10:40       ` David Disseldorp

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=20240318215955.47e408bf@echidna \
    --to=ddiss@suse.de \
    --cc=ematsumiya@suse.de \
    --cc=jack@suse.cz \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).