linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: liubo <liubo2009@cn.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>, Andreas Dilger <adilger@dilger.ca>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC PATCH] Btrfs: add ioctl to set compress or cow per file/dir
Date: Fri, 25 Feb 2011 11:33:35 +0800	[thread overview]
Message-ID: <4D67230F.6070501@cn.fujitsu.com> (raw)
In-Reply-To: <1298572774-sup-6568@think>

On 02/25/2011 02:39 AM, Chris Mason wrote:
> Excerpts from Andreas Dilger's message of 2011-02-24 13:37:52 -0500:
>> On 2011-02-24, at 2:40 AM, liubo wrote:
>>>  #define FS_DIRECTIO_FL            0x00100000 /* Use direct i/o */
>>> +#define FS_NOCOW_FL            0x00200000 /* Do not cow file */
>>> +#define FS_COW_FL            0x00100000 /* Cow file */
>>>  #define FS_RESERVED_FL            0x80000000 /* reserved for ext2 lib */
>> I'm assuming that FS_COW_FL should not be the same as FS_DIRECTIO_FL?
> 
> No, we can do DIRECTIO with COW.
> 

Sorry for my fault, thanks for pointing it out.

thanks,
liubo

> -chris
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      reply	other threads:[~2011-02-25  3:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24  9:40 [RFC PATCH] Btrfs: add ioctl to set compress or cow per file/dir liubo
2011-02-24 14:54 ` Chris Mason
2011-02-25  3:21   ` liubo
2011-02-24 18:37 ` Andreas Dilger
2011-02-24 18:39   ` Chris Mason
2011-02-25  3:33     ` liubo [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=4D67230F.6070501@cn.fujitsu.com \
    --to=liubo2009@cn.fujitsu.com \
    --cc=adilger@dilger.ca \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.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).