ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <d.phillips@partner.samsung.com>
To: Greg KH <greg@kroah.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [topic] Richer internal block API
Date: Sat, 31 May 2014 15:44:52 -0700	[thread overview]
Message-ID: <538A5B64.10203@partner.samsung.com> (raw)
In-Reply-To: <20140529234311.GB12450@kroah.com>

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. 
The larger issue would be, why is there no design process in Linux for 
large design issues? Maybe that is the core topic that is really missing.

Regards,

Daniel

  reply	other threads:[~2014-05-31 22:44 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 [this message]
2014-06-01  2:34             ` Greg KH
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=538A5B64.10203@partner.samsung.com \
    --to=d.phillips@partner.samsung.com \
    --cc=greg@kroah.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