linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: viro@zeniv.linux.org.uk, josef@redhat.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] fallocate should be a file operation
Date: Fri, 14 Jan 2011 08:12:19 -0500	[thread overview]
Message-ID: <20110114131219.GB2558@localhost.localdomain> (raw)
In-Reply-To: <20110114120743.GB13936@lst.de>

On Fri, Jan 14, 2011 at 01:07:43PM +0100, Christoph Hellwig wrote:
> Currently all filesystems except XFS implement fallocate asynchronously,
> while XFS forced a commit.  Both of these are suboptimal - in case of O_SYNC
> I/O we really want our allocation on disk, especially for the !KEEP_SIZE
> case where we actually grow the file with user-visible zeroes.  On the
> other hand always commiting the transaction is a bad idea for fast-path
> uses of fallocate like for example in recent Samba versions.   Given
> that block allocation is a data plane operation anyway change it from
> an inode operation to a file operation so that we have the file structure
> available that lets us check for O_SYNC.
> 
> This also includes moving the code around for a few of the filesystems,
> and remove the already unnedded S_ISDIR checks given that we only wire
> up fallocate for regular files.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> 

Everything looks right,

Reviewed-by: Josef Bacik <josef@redhat.com>

Thanks,

Josef

      reply	other threads:[~2011-01-14 13:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 12:07 [PATCH 2/2] fallocate should be a file operation Christoph Hellwig
2011-01-14 13:12 ` Josef Bacik [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=20110114131219.GB2558@localhost.localdomain \
    --to=josef@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).