public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kluba, Patrik" <pajko@halom.u-szeged.hu>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ferenc Havasi <havasi@inf.u-szeged.hu>,
	"Artem B. Bityuckiy" <dedekind@yandex.ru>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Michal Ludvig <michal@logix.cz>
Subject: cryptoapi compression modules & JFFSx
Date: Thu, 23 Jun 2005 19:33:37 +0000	[thread overview]
Message-ID: <1119555217l.7540l.1l@detonator> (raw)


Hi everybody,

I'm going to port JFFS2's compression modules to CryptoApi except  
{in|de}flate, which Artem is working(?) on.
I've noticed that the pcompress thing (slen <-> *slen and partial  
compression which about a discussion was on the list) is in Herbert's  
repository. Does it mean that it will get into the kernel once? I just  
would like to be sure whether should I implement pcompress or not.

The second thing is that we would like to use CryptoApi from user  
space. This way it won't be necessary to reimplement compression  
algorithms in user space filesystem image creation programs  
(mkfs.jffsx), and it would make using & distributing closed-source  
proprietary compression methods easier.
There's a patch at http://www.logix.cz/michal/devel/cryptodev/, written  
by Michal Ludvig, which adds a /dev/crypto device for this purpose, as  
on *BSD. Is there a chance that this can get into the kernel?

Regards,

   Patrik Kluba


             reply	other threads:[~2005-06-23 19:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 19:33 Kluba, Patrik [this message]
2005-06-23 21:38 ` cryptoapi compression modules & JFFSx Herbert Xu
2005-06-24  7:36 ` Artem B. Bityuckiy

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=1119555217l.7540l.1l@detonator \
    --to=pajko@halom.u-szeged.hu \
    --cc=dedekind@yandex.ru \
    --cc=havasi@inf.u-szeged.hu \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal@logix.cz \
    /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