From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Saket Sinha <saket.sinha89@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
lsf-pc@lists.linux-foundation.org
Subject: Re: [LSF/MM ATTEND] Stackable Union Filesystem Implementation
Date: Thu, 09 Jan 2014 16:32:05 +0900 [thread overview]
Message-ID: <523.1389252725@jrobl> (raw)
In-Reply-To: <CAK25hWOUhV2Ygs-Q3cVN-mio+BHB60zJ7J_wZZKb=hOR9mb0ug@mail.gmail.com>
Saket Sinha:
> > For such purpose, a "block device level union" (instead of filesystem
> > level union) may be an option for you, such as "dm snapshot".
> >
> I imagine that this would make things more complicated as ideally this
> should be done in a filesystem driver. Again a "block device level
> union" would all the more have lesser chances of getting this
> filesystem driver included in the mainline kernel as kernel
> maintainers prefer the drivers to be as simple as possible.
??
I am afraid that I cannot fully understand what you wrote.
If you think "dm snapshot" does not exist currently, and you or someone
else are going to develop a new feature, that is wrong. You already have
"dm snapshot" feature and you can "stack" the block devices by using it.
(cf. http://aufs.sourceforge.net/aufs2/report/sq/sq.pdf which is a bit
old)
J. R. Okajima
WARNING: multiple messages have this Message-ID (diff)
From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Saket Sinha <saket.sinha89@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
lsf-pc@lists.linux-foundation.org
Subject: Re: [LSF/MM ATTEND] Stackable Union Filesystem Implementation
Date: Thu, 09 Jan 2014 16:32:05 +0900 [thread overview]
Message-ID: <523.1389252725@jrobl> (raw)
In-Reply-To: <CAK25hWOUhV2Ygs-Q3cVN-mio+BHB60zJ7J_wZZKb=hOR9mb0ug@mail.gmail.com>
Saket Sinha:
> > For such purpose, a "block device level union" (instead of filesystem
> > level union) may be an option for you, such as "dm snapshot".
> >
> I imagine that this would make things more complicated as ideally this
> should be done in a filesystem driver. Again a "block device level
> union" would all the more have lesser chances of getting this
> filesystem driver included in the mainline kernel as kernel
> maintainers prefer the drivers to be as simple as possible.
??
I am afraid that I cannot fully understand what you wrote.
If you think "dm snapshot" does not exist currently, and you or someone
else are going to develop a new feature, that is wrong. You already have
"dm snapshot" feature and you can "stack" the block devices by using it.
(cf. http://aufs.sourceforge.net/aufs2/report/sq/sq.pdf which is a bit
old)
J. R. Okajima
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-01-09 7:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 10:34 [LSF/MM ATTEND] Stackable Union Filesystem Implementation Saket Sinha
2014-01-07 12:23 ` Jan Kara
2014-01-07 20:04 ` Saket Sinha
2014-01-08 5:10 ` J. R. Okajima
2014-01-08 5:10 ` J. R. Okajima
2014-01-08 18:06 ` Saket Sinha
2014-01-09 7:32 ` J. R. Okajima [this message]
2014-01-09 7:32 ` J. R. Okajima
2014-01-09 9:19 ` Saket Sinha
2014-01-09 14:17 ` J. R. Okajima
2014-01-11 17:21 ` Saket Sinha
2014-01-08 11:16 ` Jan Kara
2014-01-08 11:16 ` Jan Kara
2014-01-08 18:26 ` Saket Sinha
2014-01-08 21:26 ` Jan Kara
2014-01-09 10:06 ` Saket Sinha
2014-01-07 16:52 ` J. R. Okajima
2014-01-07 20:21 ` Saket Sinha
-- strict thread matches above, loose matches on Subject: below --
2014-01-07 10:32 Saket Sinha
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=523.1389252725@jrobl \
--to=hooanon05g@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=saket.sinha89@gmail.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 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.