linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: tag pages for writeback in sync
Date: Fri, 15 Jul 2011 20:47:23 -0400	[thread overview]
Message-ID: <4E20DF9B.8010003@redhat.com> (raw)
In-Reply-To: <20110715215011.GA32601@infradead.org>

On 07/15/2011 05:50 PM, Christoph Hellwig wrote:
> 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?

I looked at it, but we need to be able to call a special helper to lock 
the page for our btree pages, and we can queue up a bio in order to add 
pages to it from delalloc which we will submit if we have to wait on a 
page to complete writeback.  Maybe I can use the block plugging stuff 
instead of our bio thing so that if we have to wait it will get flushed 
automatically, then that just leaves our locking thing which I guess 
would be ok to pass down to write_cache_pages?  Thanks,

Josef

      reply	other threads:[~2011-07-16  0:47 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
2011-07-16  0:47   ` 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=4E20DF9B.8010003@redhat.com \
    --to=josef@redhat.com \
    --cc=hch@infradead.org \
    --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).