From: Jan Kara <jack@suse.cz>
To: Enzo Matsumiya <ematsumiya@suse.de>
Cc: 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: Fri, 15 Mar 2024 13:22:31 +0100 [thread overview]
Message-ID: <20240315122231.ktyx3ebd5mulo5or@quack3> (raw)
In-Reply-To: <rnx34bfst5gyomkwooq2pvkxsjw5mrx5vxszhz7m4hy54yuma5@huwvwzgvrrru>
Hello Enzo,
it is good to also CC appropriate public mailing lists so that other
attendees can discuss about your proposal. Added some I found relevant.
Honza
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?
>
> - overlapping modules/areas that have the need/desire to compress
> transmitting data and their status quo in the topic; difficulties
> where I could help and/or achievements that I could learn from
>
>
> Cheers,
>
> Enzo
> _______________________________________________
> Lsf-pc mailing list
> Lsf-pc@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lsf-pc
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next parent reply other threads:[~2024-03-15 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rnx34bfst5gyomkwooq2pvkxsjw5mrx5vxszhz7m4hy54yuma5@huwvwzgvrrru>
2024-03-15 12:22 ` Jan Kara [this message]
2024-03-18 10:59 ` [Lsf-pc] [LSF/MM ATTEND] Over-the-wire data compression David Disseldorp
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=20240315122231.ktyx3ebd5mulo5or@quack3 \
--to=jack@suse.cz \
--cc=ematsumiya@suse.de \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).