From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux FS Dev Mailing List <linux-fsdevel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [GIT PULL] f2fs for 4.8
Date: Wed, 27 Jul 2016 14:24:21 -0700 [thread overview]
Message-ID: <20160727212421.GA74234@jaegeuk> (raw)
In-Reply-To: <20160727084101.GA11784@infradead.org>
On Wed, Jul 27, 2016 at 01:41:01AM -0700, Christoph Hellwig wrote:
> > - ioctl to move a range of data between files
>
> Please run this through the linux-api list first. We had so many
> problem with random ioctls on random file systems in the past. Also
> I know Samsung had an xfs (and maybe ext4?) implementation of this
> functionality in the past, so it would be extremtly useful to have
> some discussion on that.
>
> Also didn't this just show up last week for the first time?
Since I couldn't defend its confident use cases right now, I thought f2fs'd be
good to support it in order for someone to evaluate it; I expected some
kv-stores tho.
Once getting its validation, let me take a look at other file systems to expose
it into a generic one.
Thanks,
next prev parent reply other threads:[~2016-07-27 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 4:08 [GIT PULL] f2fs for 4.8 Jaegeuk Kim
2016-07-27 8:41 ` Christoph Hellwig
2016-07-27 21:24 ` Jaegeuk Kim [this message]
2016-07-27 17:46 ` Linus Torvalds
2016-07-27 18:29 ` Jens Axboe
2016-07-27 18:46 ` Linus Torvalds
2016-07-27 18:47 ` Jens Axboe
2016-07-27 21:02 ` Jaegeuk Kim
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=20160727212421.GA74234@jaegeuk \
--to=jaegeuk@kernel.org \
--cc=hch@infradead.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).