linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Graeme Sheppard <nodes@rillion.net>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Patent or not patent a new idea
Date: Tue, 26 Jun 2007 13:38:58 +1000	[thread overview]
Message-ID: <18048.35410.896207.686311@notabene.brown> (raw)
In-Reply-To: message from Graeme Sheppard on Tuesday June 26

On Tuesday June 26, nodes@rillion.net wrote:
> Neil Brown wrote:
> > 
> > Sounds a lot like "RAIF" - ask google for details.
> 
> I did not know about RAIF. RAIF "merges" separate filesystems? That is a
> good idea in itself.
> 
> My idea is for driver that provides a filesystem from image files it
> controls. Because it knows these resources it uses access in tandem to
> attain performance.

???
(reads original description in more detail).

So... the filesystem images are identical in both copies, and the
"interesting" bit is that the image is just a file on some filesystem.

So could I implement your idea by:

  dd if=/dev/zero of=/1/bigfile count=lotsandlots
  dd if=/dev/zero of=/2/bigfile count=lotsandlots
  losetup /dev/loop1 /1/bigfile
  losetup /dev/loop2 /2/bigfile
  mdadm -C /dev/md0 --level=raid1 --raid-disks=2 /dev/loop1 /dev/loop2
  mkfs /dev/md0
  mount /dev/md2 /space

??

Why would you bother?  Well, I do it a lot of code testing, but I
would be hard pressed to make a case for that sort of config in
production.

You said:
>  1) the disks need
>    not be the same size or from the same manufacturer; 2) the supporting code
>    would be cross-platform.

md/raid already works happily with different sized drives from
different manufacturers (for raid1, it only uses as much space as the smaller
drive provides, For raid0 it uses it all).
I don't know what you mean by '2'.

So I still cannot see anything particularly new.  What am I missing?

NeilBrown

  reply	other threads:[~2007-06-26  3:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 21:45 Patent or not patent a new idea Graeme Sheppard
2007-06-25 22:04 ` alan
2007-06-25 22:26   ` Graeme Sheppard
2007-06-25 22:33     ` alan
2007-06-25 22:34 ` Attila Kinali
2007-06-25 22:37 ` manningc2
2007-06-26  0:11   ` Bryan Henderson
2007-06-26  1:32 ` Graeme Sheppard
2007-06-26  2:20   ` Neil Brown
2007-06-26  3:20     ` Graeme Sheppard
2007-06-26  3:38       ` Neil Brown [this message]
2007-06-26  4:22         ` Graeme Sheppard
2007-06-26  4:33           ` Neil Brown
2007-06-26 16:53         ` Bryan Henderson
2007-06-26 17:38           ` Andreas Dilger

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=18048.35410.896207.686311@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nodes@rillion.net \
    /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).