All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] fs-writeback: Add helper function to start writeback   if idle
Date: Fri, 18 Dec 2009 16:33:36 +0100	[thread overview]
Message-ID: <20091218153336.GR4489@kernel.dk> (raw)
In-Reply-To: <4B2B9FF5.4030102@redhat.com>

On Fri, Dec 18 2009, Eric Sandeen wrote:
> Jens Axboe wrote:
> > On Fri, Dec 11 2009, Eric Sandeen wrote:
> >> ext4, at least, would like to start pushing on writeback if it starts
> >> to get close to ENOSPC when reserving worst-case blocks for delalloc
> >> writes.  Writing out delalloc data will convert those worst-case
> >> predictions into usually smaller actual usage, freeing up space
> >> before we hit ENOSPC based on this speculation.
> >>
> >> Thanks to Jens for the suggestion for the helper function,
> >> & the naming help.
> >>
> >> I've made the helper return status on whether writeback was
> >> started even though I don't plan to use it in the ext4 patch;
> >> it seems like it would be potentially useful to test this
> >> in some cases.
> > 
> > Eric, how do you want to merge these? I can easily take this first one
> > through any branch, but I suppose the ext4 one should go through the
> > proper ext4 channels.
> 
> Doesn't matter to me really; maybe it'd be simpler if it all went
> though the ext4 tree so that there aren't any ordering problems?

Definately :-)

-- 
Jens Axboe


  reply	other threads:[~2009-12-18 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 23:05 [PATCH 1/2] fs-writeback: Add helper function to start writeback if idle Eric Sandeen
2009-12-16 20:44 ` Jan Kara
2009-12-18 11:44 ` Jens Axboe
2009-12-18 15:29   ` Eric Sandeen
2009-12-18 15:33     ` Jens Axboe [this message]
2009-12-23 13:00       ` tytso

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=20091218153336.GR4489@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.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.