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:43:09 -0700 [thread overview]
Message-ID: <53877FBD.7060003@partner.samsung.com> (raw)
In-Reply-To: <20140529182341.GA6410@kroah.com>
On 05/29/2014 11:23 AM, Greg KH wrote:
> On Thu, May 29, 2014 at 11:13:25AM -0700, Daniel Phillips wrote:
>> ...I wonder though, why
>> power management is regarded as a summit-worthy topic, but core
>> functionality of the block layer is not.
> power management covers the whole tree, the block layer is "just" the
> block layer.
Power management does not cover more of the tree than the block layer
plus memory management plus filesystem plus vfs do, all of which are
impacted, and all of which raise user visible API questions.
>
>>>> 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.
> Good, post patches then :)
>
> greg k-h
Is that a recommendation to develop a core API extension in a vacuum?
Regards,
Daniel
next prev parent reply other threads:[~2014-05-29 18:43 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 [this message]
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=53877FBD.7060003@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