All of lore.kernel.org
 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: Thu, 29 May 2014 11:13:25 -0700	[thread overview]
Message-ID: <538778C5.7010505@partner.samsung.com> (raw)
In-Reply-To: <20140529181319.GA24218@kroah.com>

On 05/29/2014 11:13 AM, Greg KH wrote:
> On Thu, May 29, 2014 at 10:49:13AM -0700, Daniel Phillips wrote:
>> Hi Neil,
>>
>> This will be my annual proposal to open a general discussion about improving
>> the internal block API, to be capable of doing all the things that the ZFS
>> crowd claim are impossible without rampantly violating filesystem/raid
>> layering. Attacking this in a storage-specific venue would also be good,
>> however I view this issue as being at least as central as a number of topics
>> already raised for general consideration.
> Why didn't you bring this up at the filesystem summit a few months ago?
> That's the best place for it, not at the kernel summit.
Sorry, I did not have time to participate this year. I wonder though, 
why power management is regarded as a summit-worthy topic, but core 
functionality of the block layer is not.
>
>> Full disclosure dept: I have an agenda. I want to add the equivalent of
>> Raidz etc to Tux3 without reimplementing a logical volume manager in the
>> filesystem.
> Like btrfs is doing?  :)
>
> greg k-h
Not like btrfs is doing, the opposite really.

Regards,

Daniel

  reply	other threads:[~2014-05-29 18:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 17:49 [Ksummit-discuss] [topic] Richer internal block API Daniel Phillips
2014-05-29 18:13 ` Greg KH
2014-05-29 18:13   ` Daniel Phillips [this message]
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
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=538778C5.7010505@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 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.