Tell the page allocator that pages allocated for a buffered write are
expected to become dirty soon.
Signed-off-by: Johannes Weiner jwei...@redhat.com
---
fs/btrfs/file.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c
index
*if you use ntfs-3g copy files larger than main memory
or: per-zone dirty limits
There have been several discussions and patches around the issue of
dirty pages being written from page reclaim, that is, they reach the
end of the LRU list before they are cleaned.
Proposed reasons for this are
The amount of dirtyable pages should not include the total number of
free pages: there is a number of reserved pages that the page
allocator and kswapd always try to keep free.
The closer (reclaimable pages - dirty pages) is to the number of
reserved pages, the more likely it becomes for reclaim
This patch allows allocators to pass __GFP_WRITE when they know in
advance that the allocated page will be written to and become dirty
soon. The page allocator will then attempt to distribute those
allocations across zones, such that no single zone will end up full of
dirty, and thus more or
On Tue, Sep 20, 2011 at 03:45:15PM +0200, Johannes Weiner wrote:
Tell the page allocator that pages allocated for a buffered write are
expected to become dirty soon.
Signed-off-by: Johannes Weiner jwei...@redhat.com
---
fs/btrfs/file.c |2 +-
1 files changed, 1 insertions(+), 1
On 09/20/2011 09:56 AM, Johannes Weiner wrote:
On Tue, Sep 20, 2011 at 03:45:15PM +0200, Johannes Weiner wrote:
Tell the page allocator that pages allocated for a buffered write are
expected to become dirty soon.
Signed-off-by: Johannes Weiner jwei...@redhat.com
---
fs/btrfs/file.c |2
On Tue, Sep 20, 2011 at 10:09:38AM -0400, Josef Bacik wrote:
On 09/20/2011 09:56 AM, Johannes Weiner wrote:
On Tue, Sep 20, 2011 at 03:45:15PM +0200, Johannes Weiner wrote:
Tell the page allocator that pages allocated for a buffered write are
expected to become dirty soon.
In addition to regular write shouldn't __do_fault and do_wp_page also
calls this if they are called on file backed mappings?
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Mon, Sep 19, 2011 at 10:53:45AM +0800, Li Zefan wrote:
With compress option specified, btrfs will try to compress the file, at most
128K at one time, and if the compressed result is not smaller, the file will
be marked as uncompressable.
I just tried with Fedora-14-i386-DVD.iso, and the
On 09/20/2011 09:45 AM, Johannes Weiner wrote:
The amount of dirtyable pages should not include the total number of
free pages: there is a number of reserved pages that the page
allocator and kswapd always try to keep free.
The closer (reclaimable pages - dirty pages) is to the number of
Just wondering if/how one goes about getting the btrfs checksum of a given
file. Is there a way?
Thanks!
-Ken
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Tue, Sep 20, 2011 at 11:24:30AM -0400, Ken D'Ambrosio wrote:
Just wondering if/how one goes about getting the btrfs checksum of a given
file. Is there a way?
Checksums are computed on individual 4k blocks, not on the whole
file. There's no explicit interface for retrieving checksums, but
[Your Reply-to: header was screwed up, so I'm sending this again.
From: Ken D'Ambrosio k...@jots.org
Reply-to: File's...@jots.org, checksum?@jots.org
]
On Tue, Sep 20, 2011 at 04:35:40PM +0100, Hugo Mills wrote:
On Tue, Sep 20, 2011 at 11:24:30AM -0400, Ken D'Ambrosio wrote:
Just
Hi Chris-
This pull misses the clone reservation fix again... :)
http://www.spinics.net/lists/linux-btrfs/msg11826.html
Thanks!
sage
On Mon, 19 Sep 2011, Chris Mason wrote:
Hi everyone,
The for-linus branch of the btrfs tree on github:
Head commit:
On 09/20/2011 09:45 AM, Johannes Weiner wrote:
This patch allows allocators to pass __GFP_WRITE when they know in
advance that the allocated page will be written to and become dirty
soon. The page allocator will then attempt to distribute those
allocations across zones, such that no single zone
On 09/20/2011 10:25 AM, Christoph Hellwig wrote:
In addition to regular write shouldn't __do_fault and do_wp_page also
calls this if they are called on file backed mappings?
Probably not do_wp_page since it always creates an
anonymous page, which are not very relevant to the
dirty page cache
On Tue, Sep 20, 2011 at 02:38:03PM -0400, Rik van Riel wrote:
On 09/20/2011 10:25 AM, Christoph Hellwig wrote:
In addition to regular write shouldn't __do_fault and do_wp_page also
calls this if they are called on file backed mappings?
Probably not do_wp_page since it always creates an
On 09/20/2011 09:45 AM, Johannes Weiner wrote:
Tell the page allocator that pages allocated for a buffered write are
expected to become dirty soon.
Signed-off-by: Johannes Weinerjwei...@redhat.com
Reviewed-by: Rik van Riel r...@redhat.com
--
To unsubscribe from this list: send the line
Sage mentioned I was missing a patch. So I've retested and updated the
git tree. Since Linus did pull my tree yesterday, here's a new pull
request with the single commit.
Linus I have this in two flavors. One is merged on top of my for-linus
branch, which was 3.1-rc6 + my last pull request:
On Mon, 2011-09-19 at 02:44 +0200, Maciej Marcin Piechotka wrote:
On Tue, 2011-08-30 at 14:27 +0800, Miao Xie wrote:
Unfortunately it results in freeze of system and I cannot give more
details. Sometimes it happens not from fcron but then it does not result
in freeze (???).
20 matches
Mail list logo
