mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Pavel Machek <pavel@ucw.cz>
Cc: Rik van Riel <riel@surriel.com>, linux-kernel@vger.kernel.org
Subject: Re: WANTED: kernel projects for CS students
Date: Mon, 29 Oct 2007 15:48:20 -0400	[thread overview]
Message-ID: <20071029194820.GC27646@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20071028180707.GA6111@ucw.cz>

On Sun, Oct 28, 2007 at 06:07:07PM +0000, Pavel Machek wrote:
> Hard stuff:
> 
> * network character device -- similar to nbd, but for char devices.
>   either figure out how to forward ioctls(), or implement
>   usb-over-network, or...
> 
> * openMosix -- they seem to have userspace solution, but not GPLed.
> 
> * compression for ext4. Its about time someone did it right. Special
>   bonus if you can do it in a way that it does not slow down. If cpu
>   is free, compress, if it is busy, just write it straight to disk.

So if I decide that the cpu is busy (because something is asking me to
write the cpu is clearly doing something and hence busy), then I can
skip compression and just write to disk.  So by that definition ext4
already does compression.  What a simple project. :)

Did you mean it ought to come back and do the compression later?

Is it possible that for some data compressing it and writing will take
less time than not compressing it and writing it to disk?

--
Len Sorensen

  parent reply	other threads:[~2007-10-29 19:49 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14 23:01 Rik van Riel
2007-10-15 10:40 ` WANG Cong
2007-10-15 17:13   ` Rik van Riel
2007-10-15 14:23 ` Sam Ravnborg
2007-10-15 15:10   ` Rik van Riel
2007-10-15 18:31     ` Sam Ravnborg
2007-10-15 16:31   ` Philippe Elie
2007-10-15 16:36     ` Philippe Elie
2007-10-15 16:52       ` Jan Engelhardt
2007-10-15 16:53       ` Xavier Bestel
2007-10-15 18:19     ` Sam Ravnborg
2007-10-15 15:40 ` Jörn Engel
2007-10-15 17:04 ` Doug Whitesell (LKML)
2007-10-15 17:04 ` Mark Gross
2007-10-15 18:30   ` Sam Ravnborg
2007-10-15 18:45     ` Mark Gross
2007-10-15 19:54     ` Giacomo Catenazzi
2007-10-16 20:06       ` Mark Gross
2007-10-16 20:09         ` Jan Engelhardt
2007-10-16 20:23           ` Rik van Riel
2007-10-16 20:25             ` Jan Engelhardt
2007-10-16 21:10               ` david
2007-10-16 21:30             ` david
2007-11-02  7:54             ` Giacomo Catenazzi
2007-10-16 20:31           ` Giacomo Catenazzi
2007-10-15 19:17   ` Alexey Dobriyan
2007-10-15 19:54     ` Folkert van Heusden
2007-10-16 20:10     ` Mark Gross
2007-10-16  0:39   ` david
2007-10-15 17:10 ` Zan Lynx
2007-10-15 17:23   ` Rik van Riel
2007-10-16  0:51   ` david
2007-10-15 17:30 ` Guilherme Amadio
2007-10-15 18:03   ` J. Bruce Fields
2007-10-17 17:45 ` Mark Gross
2007-10-18  4:51 ` Toshiharu Harada
2007-10-28 18:07 ` Pavel Machek
2007-10-28 18:57   ` Rafael J. Wysocki
2007-10-29 19:48   ` Lennart Sorensen [this message]
2007-10-29 20:19     ` Pavel Machek
2007-10-29 21:44       ` Lennart Sorensen
2007-11-03  3:08         ` Valdis.Kletnieks
2007-11-03  3:36           ` Rik van Riel
2007-11-03  9:44             ` Wander Winkelhorst
2007-11-03 10:05             ` david

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=20071029194820.GC27646@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=riel@surriel.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

all inboxes | Powered by JetHome®