From: Seth Forshee <seth.forshee@canonical.com>
To: Aleksa Sarai <asarai@suse.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
containers@lists.linux-foundation.org,
linux-fsdevel@vger.kernel.org,
Tyler Hicks <tyler.hicks@canonical.com>,
Christian Brauner <christian.brauner@canonical.com>
Subject: Re: shiftfs status and future development
Date: Fri, 15 Jun 2018 10:05:17 -0500 [thread overview]
Message-ID: <20180615150517.GG30028@ubuntu-xps13> (raw)
In-Reply-To: <20180615145438.pf6g7u35lt52aapw@gordon>
On Sat, Jun 16, 2018 at 12:54:38AM +1000, Aleksa Sarai wrote:
> On 2018-06-14, Seth Forshee <seth.forshee@canonical.com> wrote:
> > I wanted to inquire about the current status of shiftfs and the plans
> > for it moving forward. We'd like to have this functionality available
> > for use in lxd, and I'm interesetd in helping with development (or
> > picking up development if it's stalled).
> >
> > To start, is anyone still working on shiftfs or similar functionality? I
> > haven't found it in any git tree on kernel.org, and as far as mailing
> > list activity the last submission I can find is [1]. Is there anything
> > newer than this?
>
> James Bottomley demoed the current status of shiftfs at the last Linux
> Plumbers' Conference. Personally, it looked like some of the motivations
> behind why we needed a shiftfs (and what it should look like) were lost
> over time, and the result is that the patchset mutated and has
> effectively stalled development for over a year (as far as I know it
> hasn't been posted again in over a year, and nobody is carrying it in
> their tree).
That's my impression too, which I was attempting to confirm with my mail
:-)
> I agree with Serge that if we want to restart its development someone
> should write down what the requirements and goals are to avoid having a
> patchset which mutates over many review cycles.
I agree, though some evolution during review is inevitable. I just
responed to Serge with some of our requirements, if you have some to add
I'd love to see them.
Thanks,
Seth
next prev parent reply other threads:[~2018-06-15 15:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 18:44 shiftfs status and future development Seth Forshee
2018-06-15 13:56 ` Serge E. Hallyn
2018-06-15 14:59 ` Seth Forshee
2018-06-15 15:25 ` Matthew Wilcox
2018-06-15 15:56 ` Aleksa Sarai
2018-06-15 16:09 ` James Bottomley
2018-06-15 17:04 ` Aleksa Sarai
2018-06-15 17:22 ` James Bottomley
2018-06-15 20:47 ` Seth Forshee
2018-06-15 21:09 ` James Bottomley
2018-06-15 21:35 ` Seth Forshee
2018-06-16 3:03 ` James Bottomley
2018-06-18 13:40 ` Seth Forshee
2018-06-18 13:49 ` Amir Goldstein
2018-06-18 14:56 ` James Bottomley
2018-06-18 16:03 ` Seth Forshee
2018-06-18 17:11 ` Amir Goldstein
2018-06-18 19:53 ` Phil Estes
2018-06-21 20:16 ` Seth Forshee
2018-06-24 11:32 ` Amir Goldstein
2018-06-25 11:19 ` Christian Brauner
2018-06-27 7:48 ` James Bottomley
2018-06-27 10:17 ` Amir Goldstein
2018-07-03 16:54 ` Serge E. Hallyn
2018-07-03 17:08 ` Stéphane Graber
2018-07-03 22:05 ` Serge E. Hallyn
2018-06-15 14:54 ` Aleksa Sarai
2018-06-15 15:05 ` Seth Forshee [this message]
2018-06-15 15:28 ` James Bottomley
2018-06-15 15:46 ` Seth Forshee
2018-06-15 16:16 ` Christian Brauner
2018-06-15 16:35 ` James Bottomley
2018-06-15 20:17 ` Seth Forshee
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=20180615150517.GG30028@ubuntu-xps13 \
--to=seth.forshee@canonical.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=asarai@suse.de \
--cc=christian.brauner@canonical.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tyler.hicks@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).