mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: Lei Yang <leiyang@nec-labs.com>
Cc: Phillip Lougher <phillip@lougher.demon.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Compression algorithm in cloop
Date: Wed, 11 Aug 2004 19:24:42 +0100	[thread overview]
Message-ID: <411A646A.5040702@grupopie.com> (raw)
In-Reply-To: <411A5E55.3050508@nec-labs.com>

Lei Yang wrote:
> 
> If I don't want to build a new compression library and port it to 
> kernel, all I want to do is to try out the idea -- whether it could work 
> on cloop, whether the compression ratio is acceptable, can I just change 
> the cloop code? In other words, I just need a loopback block device with 
> other compression scheme.

If you just want to try out some wacky ideas, I suggest you take a look 
at the network block device.

It is a block device that sends all read/write requests through a socket 
  so that this requests can be fulfilled by a user space deamon.

This is not very good in terms of performance, but it is much easier to 
develop this kind of thing in userspace, without all the stack / memory 
/ atomicity / concurrency problems :)

-- 
Paulo Marques - www.grupopie.com
"In a world without walls and fences who needs windows and gates?"

  reply	other threads:[~2004-08-11 18:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 16:45 Phillip Lougher
2004-08-11 17:21 ` Grzegorz Kulewski
2004-08-11 17:19   ` Randy.Dunlap
2004-08-11 17:58 ` Lei Yang
2004-08-11 18:24   ` Paulo Marques [this message]
     [not found] <411A348D.9070808@nec-labs.com>
     [not found] ` <411A50CD.3070908@gentoo.org>
2004-08-11 17:19   ` Lei Yang
  -- strict thread matches above, loose matches on Subject: below --
2004-08-11 15:43 Lei Yang

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=411A646A.5040702@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=leiyang@nec-labs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillip@lougher.demon.co.uk \
    /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

Powered by JetHome