From: Omar Sandoval <osandov@osandov.com>
To: dsterba@suse.cz, Omar Sandoval <osandov@fb.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: add autodefrag inode flag
Date: Tue, 30 Jun 2015 09:24:53 -0700 [thread overview]
Message-ID: <5592C2D5.1040304@osandov.com> (raw)
In-Reply-To: <20150630161830.GI726@twin.jikos.cz>
On 06/30/2015 09:18 AM, David Sterba wrote:
> On Thu, Jun 18, 2015 at 07:10:47PM -0700, Omar Sandoval wrote:
>> In some cases, we may not want to enable automatic defragmentation for
>> the whole filesystem with the "autodefrag" mount option but we still
>> want to defragment specific files or directories. Add an inode flag
>> which allows us to do specify that.
>
> While I think all sorts of inode flags can be useful, the autodefrag is
> a good example, please note that you're touching a public interface
> header
>
>> include/uapi/linux/fs.h | 1 +
>
> so this should be discussed at fsdevel.
Ah, right, definitely. I'll resend the patch and CC fsdevel.
Thanks,
--
Omar
prev parent reply other threads:[~2015-06-30 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 2:10 [PATCH] Btrfs: add autodefrag inode flag Omar Sandoval
2015-06-30 16:18 ` David Sterba
2015-06-30 16:24 ` Omar Sandoval [this message]
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=5592C2D5.1040304@osandov.com \
--to=osandov@osandov.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@fb.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