From: Christoph Hellwig <hch@infradead.org>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: tag pages for writeback in sync
Date: Fri, 15 Jul 2011 17:50:11 -0400 [thread overview]
Message-ID: <20110715215011.GA32601@infradead.org> (raw)
In-Reply-To: <1310765198-10077-1-git-send-email-josef@redhat.com>
On Fri, Jul 15, 2011 at 05:26:38PM -0400, Josef Bacik wrote:
> Everybody else does this, we need to do it too. If we're syncing, we need to
> tag the pages we're going to write for writeback so we don't end up writing the
> same stuff over and over again if somebody is constantly redirtying our file.
> This will keep us from having latencies with heavy sync workloads. Thanks,
Maybe it's time to find a wait to merge the btrfs copy of write_cache_pages
back into the main one?
next prev parent reply other threads:[~2011-07-15 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 21:26 [PATCH] Btrfs: tag pages for writeback in sync Josef Bacik
2011-07-15 21:50 ` Christoph Hellwig [this message]
2011-07-16 0:47 ` Josef Bacik
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=20110715215011.GA32601@infradead.org \
--to=hch@infradead.org \
--cc=josef@redhat.com \
--cc=linux-btrfs@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).