From: Greg KH <greg@kroah.com>
To: Daniel Phillips <d.phillips@partner.samsung.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [topic] Richer internal block API
Date: Sat, 31 May 2014 19:34:58 -0700 [thread overview]
Message-ID: <20140601023458.GA5243@kroah.com> (raw)
In-Reply-To: <538A5B64.10203@partner.samsung.com>
On Sat, May 31, 2014 at 03:44:52PM -0700, Daniel Phillips wrote:
> On 05/29/2014 04:43 PM, Greg KH wrote:
> >...you know how this all works, we don't have to have meetings in order to
> >do design decisions that are "large".
>
>
> Perhaps there is something wrong with that approach. Certainly in regards to
> how to bridge the gap between what we now have for logical volume support,
> and what we should have, or what BSD has, that approach is demonstrably a
> perennial failure. After all these years, we still have dm and md as
> separate islands, no usable snapshotting block device, and roughly zero
> interaction between filesystems and volume managers.
People have talked about this for over a very long time. I've seen
Neil give numerous presentations about this for what, a decade now?
It must not be important enough for anyone to actually do the work. Or,
more likely, no one has been able to convince a company to sponsor the
work. So perhaps, it isn't that major of a thing that is needed to be
done?
> The larger issue would be, why is there no design process in Linux for
> large design issues?
There is, an "evolutionary" process. If you take a look at a 4 or 5
year old kernel, major things have happened. It's just that if you are
in the middle of it all, it doesn't look like "large" things have
changed.
thanks,
greg k-h
next prev parent reply other threads:[~2014-06-01 2:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 17:49 Daniel Phillips
2014-05-29 18:13 ` Greg KH
2014-05-29 18:13 ` Daniel Phillips
2014-05-29 18:23 ` Greg KH
2014-05-29 18:43 ` Daniel Phillips
2014-05-29 23:43 ` Greg KH
2014-05-31 22:44 ` Daniel Phillips
2014-06-01 2:34 ` Greg KH [this message]
2014-06-02 17:33 ` Martin K. Petersen
2014-06-02 18:10 ` James Bottomley
2014-06-01 4:31 ` NeilBrown
2014-05-30 9:56 ` Lukáš Czerner
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=20140601023458.GA5243@kroah.com \
--to=greg@kroah.com \
--cc=d.phillips@partner.samsung.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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