From: Theodore Ts'o <tytso@mit.edu>
To: 宋柏翰 <solarispika@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Question on delalloc
Date: Tue, 4 Jun 2013 01:22:03 -0400 [thread overview]
Message-ID: <20130604052203.GA29587@thunk.org> (raw)
In-Reply-To: <CAJ1XODTmBmdOu+EL8OZy8ZRU4DbT7F179U7BrNDrQJQGtYQuWw@mail.gmail.com>
On Tue, Jun 04, 2013 at 03:00:29AM +0800, 宋柏翰 wrote:
> Also after I traced into filemap_write_and_wait_range, I found it
> eventually calls ext4_writepage to do the most part of work, which in
> its comment says "We don't do any block allocation in this function."
>
> So, can anyone kindly shed any light on my question, or point out my mistakes?
There are three possible address_space_operations structures that can
be used for ext4 files. They are ext4_aops, ext4_journalled_aops, and
ext4_da_aops. It is the last one which is used for delayed allocation
files, and in that case filemap_write_and_wait_range will use
ext4_da_writepages().
These days, if there is an writepages function, the writepage function
is not used at all. It used to be used for direct reclaim, but that's
been replaced by I/O-less reclaim.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-06-04 5:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 19:00 Question on delalloc 宋柏翰
2013-06-04 5:22 ` Theodore Ts'o [this message]
2013-06-04 14:26 ` Eric Sandeen
2013-06-04 17:30 ` 宋柏翰
2013-06-04 19:01 ` Theodore Ts'o
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=20130604052203.GA29587@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=solarispika@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.