From: Lars Marowsky-Bree <lmb@suse.de>
To: Heinz Mauelshagen <mauelshagen@redhat.com>
Cc: Neil Brown <neilb@suse.de>, Phillip Susi <psusi@cfl.rr.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
"Lincoln Dale (ltd)" <ltd@cisco.com>,
Michael Tokarev <mjt@tls.msk.ru>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
"Steinar H. Gunderson" <sgunderson@bigfoot.com>
Subject: Re: [PATCH 000 of 5] md: Introduction
Date: Mon, 23 Jan 2006 11:45:22 +0100 [thread overview]
Message-ID: <20060123104522.GE2366@marowsky-bree.de> (raw)
In-Reply-To: <20060123103851.GY2801@redhat.com>
On 2006-01-23T11:38:51, Heinz Mauelshagen <mauelshagen@redhat.com> wrote:
> > Ok, I still didn't get that. I must be slow.
> >
> > Did you implement some DM-internal stacking now to avoid the above
> > mentioned complexity?
> >
> > Otherwise, even DM-on-DM is still stacked via the block device
> > abstraction...
>
> No, not necessary because a single-level raid4/5 mapping will do it.
> Ie. it supports <offset> parameters in the constructor as other targets
> do as well (eg. mirror or linear).
An dm-md wrapper would not support such a basic feature (which is easily
added to md too) how?
I mean, "I'm rewriting it because I want to and because I understand and
own the code then" is a perfectly legitimate reason, but let's please
not pretend there's really sound and good technical reasons ;-)
Sincerely,
Lars Marowsky-Brée
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Lars Marowsky-Bree <lmb@suse.de>
To: Heinz Mauelshagen <mauelshagen@redhat.com>
Cc: Neil Brown <neilb@suse.de>, Phillip Susi <psusi@cfl.rr.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
"Lincoln Dale (ltd)" <ltd@cisco.com>,
Michael Tokarev <mjt@tls.msk.ru>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
"Steinar H. Gunderson" <sgunderson@bigfoot.com>
Subject: Re: [PATCH 000 of 5] md: Introduction
Date: Mon, 23 Jan 2006 11:45:22 +0100 [thread overview]
Message-ID: <20060123104522.GE2366@marowsky-bree.de> (raw)
In-Reply-To: <20060123103851.GY2801@redhat.com>
On 2006-01-23T11:38:51, Heinz Mauelshagen <mauelshagen@redhat.com> wrote:
> > Ok, I still didn't get that. I must be slow.
> >
> > Did you implement some DM-internal stacking now to avoid the above
> > mentioned complexity?
> >
> > Otherwise, even DM-on-DM is still stacked via the block device
> > abstraction...
>
> No, not necessary because a single-level raid4/5 mapping will do it.
> Ie. it supports <offset> parameters in the constructor as other targets
> do as well (eg. mirror or linear).
An dm-md wrapper would not support such a basic feature (which is easily
added to md too) how?
I mean, "I'm rewriting it because I want to and because I understand and
own the code then" is a perfectly legitimate reason, but let's please
not pretend there's really sound and good technical reasons ;-)
Sincerely,
Lars Marowsky-Brée
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
next prev parent reply other threads:[~2006-01-23 10:45 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 21:38 [PATCH 000 of 5] md: Introduction Lincoln Dale (ltd)
2006-01-17 21:38 ` Lincoln Dale (ltd)
2006-01-18 13:27 ` Jan Engelhardt
2006-01-18 23:19 ` Neil Brown
2006-01-19 15:33 ` Mark Hahn
2006-01-19 15:33 ` Mark Hahn
2006-01-19 20:12 ` Jan Engelhardt
2006-01-19 21:22 ` Lars Marowsky-Bree
2006-01-19 21:22 ` Lars Marowsky-Bree
2006-01-19 22:17 ` Phillip Susi
2006-01-19 22:32 ` Neil Brown
2006-01-19 23:26 ` Phillip Susi
2006-01-19 23:43 ` Neil Brown
2006-01-20 2:17 ` Phillip Susi
2006-01-20 10:53 ` Lars Marowsky-Bree
2006-01-20 10:53 ` Lars Marowsky-Bree
2006-01-20 12:06 ` Jens Axboe
2006-01-20 18:38 ` Heinz Mauelshagen
2006-01-20 18:38 ` Heinz Mauelshagen
2006-01-20 22:09 ` Lars Marowsky-Bree
2006-01-20 22:09 ` Lars Marowsky-Bree
2006-01-21 0:06 ` Heinz Mauelshagen
2006-01-21 0:06 ` Heinz Mauelshagen
2006-01-20 18:41 ` Heinz Mauelshagen
2006-01-20 17:29 ` Ross Vandegrift
2006-01-20 17:29 ` Ross Vandegrift
2006-01-20 18:36 ` Heinz Mauelshagen
2006-01-20 22:57 ` Lars Marowsky-Bree
2006-01-20 22:57 ` Lars Marowsky-Bree
2006-01-21 0:01 ` Heinz Mauelshagen
2006-01-21 0:01 ` Heinz Mauelshagen
2006-01-21 0:03 ` Lars Marowsky-Bree
2006-01-21 0:03 ` Lars Marowsky-Bree
2006-01-21 0:08 ` Heinz Mauelshagen
2006-01-21 0:08 ` Heinz Mauelshagen
2006-01-21 0:13 ` Lars Marowsky-Bree
2006-01-23 9:44 ` Heinz Mauelshagen
2006-01-23 10:26 ` Lars Marowsky-Bree
2006-01-23 10:38 ` Heinz Mauelshagen
2006-01-23 10:38 ` Heinz Mauelshagen
2006-01-23 10:45 ` Lars Marowsky-Bree [this message]
2006-01-23 10:45 ` Lars Marowsky-Bree
2006-01-23 11:00 ` Heinz Mauelshagen
2006-01-23 11:00 ` Heinz Mauelshagen
2006-01-23 12:54 ` Ville Herva
2006-01-23 12:54 ` Ville Herva
2006-01-23 13:00 ` Steinar H. Gunderson
2006-01-23 13:54 ` Heinz Mauelshagen
2006-01-23 17:33 ` Ville Herva
2006-01-23 17:33 ` Ville Herva
2006-01-24 2:02 ` Phillip Susi
2006-01-24 7:26 ` Error message for invalid initramfs cpio format? Ville Herva
2006-01-20 7:51 ` [PATCH 000 of 5] md: Introduction Reuben Farrelly
2006-01-20 3:43 ` Andre' Breiler
2006-01-21 0:42 ` David Greaves
-- strict thread matches above, loose matches on Subject: below --
2006-01-20 18:05 Hubert Tonneau
2006-01-20 17:01 Hubert Tonneau
2006-01-20 16:15 ` Christoph Hellwig
2006-01-22 6:45 ` Herbert Poetzl
2006-01-20 16:48 Hubert Tonneau
2006-01-17 6:56 NeilBrown
2006-01-17 8:17 ` Michael Tokarev
[not found] ` <fd8d0180601170121s1e6a55b7o@mail.gmail.com>
2006-01-17 9:38 ` Francois Barre
2006-01-19 0:35 ` Neil Brown
2006-01-17 9:50 ` Sander
2006-01-17 11:26 ` Michael Tokarev
2006-01-17 11:37 ` Francois Barre
2006-01-17 14:03 ` Kyle Moffett
2006-01-19 0:28 ` Neil Brown
2006-01-17 16:08 ` Ross Vandegrift
2006-01-17 16:08 ` Ross Vandegrift
2006-01-17 18:12 ` Michael Tokarev
2006-01-17 18:12 ` Michael Tokarev
2006-01-18 8:14 ` Sander
2006-01-18 8:14 ` Sander
2006-01-18 8:37 ` Brad Campbell
2006-01-18 9:03 ` Alan Cox
2006-01-18 12:46 ` John Hendrikx
2006-01-18 12:51 ` Gordon Henderson
2006-01-18 23:51 ` Neil Brown
2006-01-19 7:20 ` PFC
2006-01-19 8:01 ` dean gaudet
2006-01-18 23:54 ` Neil Brown
2006-01-19 0:22 ` Neil Brown
2006-01-19 0:22 ` Neil Brown
2006-01-19 9:01 ` Jakob Oestergaard
2006-01-19 9:01 ` Jakob Oestergaard
2006-01-17 22:38 ` Phillip Susi
2006-01-17 22:57 ` Neil Brown
2006-01-17 14:10 ` Steinar H. Gunderson
2006-01-17 15:07 ` Mr. James W. Laferriere
2006-01-19 0:23 ` Neil Brown
2006-01-22 4:42 ` Adam Kropelin
2006-01-22 22:52 ` Neil Brown
2006-01-23 23:02 ` Adam Kropelin
2006-01-23 23:02 ` Adam Kropelin
2006-01-23 1:08 ` John Hendrikx
2006-01-23 1:25 ` Neil Brown
2006-01-23 1:54 ` Kyle Moffett
2006-01-23 2:09 ` Mr. James W. Laferriere
2006-01-23 2:33 ` Neil Brown
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=20060123104522.GE2366@marowsky-bree.de \
--to=lmb@suse.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=ltd@cisco.com \
--cc=mauelshagen@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=neilb@suse.de \
--cc=psusi@cfl.rr.com \
--cc=sgunderson@bigfoot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.