From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [PATCH, RFC] ext4: add EXT4_IOC_ALLOC_DA_BLKS ioctl
Date: Wed, 11 Mar 2009 17:41:05 -0500 [thread overview]
Message-ID: <49B83E01.1040605@redhat.com> (raw)
In-Reply-To: <1235451952-2726-5-git-send-email-tytso@mit.edu>
Theodore Ts'o wrote:
> Add an ioctl which forces all of the delay allocated blocks to be
> allocated. This also provides a function ext4_alloc_da_blocks() which
> will be used by the following commits to force files to be fully
> allocated to preserve application-expected ext3 behaviour.
>
Is it worth checking whether a) the file has delalloc blocks, and/or b)
whether the mapping is dirty before we spin off a filemap_flush?
-Eric
next prev parent reply other threads:[~2009-03-11 22:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 5:05 [PATCH, RFC] Clean up of delalloc code and map-on-close/rename fixes Theodore Ts'o
2009-02-24 5:05 ` [PATCH, RFC] ext4: Simplify delalloc implementation by removing mpd.get_block Theodore Ts'o
2009-02-24 5:05 ` [PATCH, RFC] ext4: Save stack space by removing fake buffer heads Theodore Ts'o
2009-02-24 5:05 ` [PATCH, RFC] ext4: Simplify delalloc code by removing mpage_da_writepages() Theodore Ts'o
2009-02-24 5:05 ` [PATCH, RFC] ext4: add EXT4_IOC_ALLOC_DA_BLKS ioctl Theodore Ts'o
2009-02-24 5:05 ` [PATCH, RFC] ext4: Automatically allocate delay allocated blocks on close Theodore Ts'o
2009-02-24 5:05 ` [PATCH, RFC] ext4: Automatically allocate delay allocated blocks on rename Theodore Ts'o
2009-02-24 10:13 ` [PATCH, RFC] ext4: Automatically allocate delay allocated blocks on close Andreas Dilger
2009-02-24 13:21 ` Theodore Tso
2009-02-24 9:38 ` [PATCH, RFC] ext4: add EXT4_IOC_ALLOC_DA_BLKS ioctl Aneesh Kumar K.V
2009-02-24 13:14 ` Theodore Tso
2009-02-24 10:11 ` Andreas Dilger
2009-02-24 13:16 ` Theodore Tso
2009-03-11 22:41 ` Eric Sandeen [this message]
2009-03-12 5:29 ` Aneesh Kumar K.V
2009-03-12 16:32 ` Eric Sandeen
2009-03-12 20:04 ` Theodore Tso
2009-03-12 20:05 ` Eric Sandeen
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=49B83E01.1040605@redhat.com \
--to=sandeen@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).