From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-block@vger.kernel.org, jack@suse.cz
Subject: Re: [PATCH 1/8] block: add WRITE_BACKGROUND
Date: Wed, 2 Nov 2016 10:22:03 -0600 [thread overview]
Message-ID: <20161102162203.GA7591@kernel.dk> (raw)
In-Reply-To: <20161102145520.GE13964@lst.de>
On Wed, Nov 02 2016, Christoph Hellwig wrote:
> On Tue, Nov 01, 2016 at 03:08:44PM -0600, Jens Axboe wrote:
> > This adds a new request flag, REQ_BACKGROUND, that callers can use to
> > tell the block layer that this is background (non-urgent) IO.
>
> The subject still says WRITE_BACKGROUND :)
Gah - will fix that up.
> Otherwise looks fine:
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
Added, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2016-11-02 16:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 21:08 [PATCHSET] Throttled buffered writeback Jens Axboe
2016-11-01 21:08 ` [PATCH 1/8] block: add WRITE_BACKGROUND Jens Axboe
2016-11-02 14:55 ` Christoph Hellwig
2016-11-02 16:22 ` Jens Axboe [this message]
2016-11-05 22:27 ` Jan Kara
2016-11-01 21:08 ` [PATCH 2/8] writeback: add wbc_to_write_flags() Jens Axboe
2016-11-02 14:56 ` Christoph Hellwig
2016-11-01 21:08 ` [PATCH 3/8] writeback: mark background writeback as such Jens Axboe
2016-11-02 14:56 ` Christoph Hellwig
2016-11-05 22:26 ` Jan Kara
2016-11-01 21:08 ` [PATCH 4/8] writeback: track if we're sleeping on progress in balance_dirty_pages() Jens Axboe
2016-11-02 14:57 ` Christoph Hellwig
2016-11-02 14:59 ` Jens Axboe
2016-11-02 14:59 ` Jens Axboe
2016-11-08 13:02 ` Jan Kara
2016-11-01 21:08 ` [PATCH 5/8] block: add code to track actual device queue depth Jens Axboe
2016-11-02 14:59 ` Christoph Hellwig
2016-11-02 15:02 ` Jens Axboe
2016-11-02 15:02 ` Jens Axboe
2016-11-02 16:40 ` Johannes Thumshirn
2016-11-02 16:40 ` Johannes Thumshirn
2016-11-05 22:37 ` Jan Kara
2016-11-01 21:08 ` [PATCH 6/8] block: add scalable completion tracking of requests Jens Axboe
2016-11-08 13:30 ` Jan Kara
2016-11-08 15:25 ` Jens Axboe
2016-11-09 9:01 ` Jan Kara
2016-11-09 16:09 ` Jens Axboe
2016-11-09 16:09 ` Jens Axboe
2016-11-09 19:52 ` Jens Axboe
2016-11-10 19:38 ` Jan Kara
2016-11-12 5:19 ` Jens Axboe
2016-11-01 21:08 ` [PATCH 7/8] blk-wbt: add general throttling mechanism Jens Axboe
2016-11-08 13:39 ` Jan Kara
2016-11-08 15:41 ` Jens Axboe
2016-11-09 8:40 ` Jan Kara
2016-11-09 16:07 ` Jens Axboe
2016-11-09 19:52 ` Jens Axboe
2016-11-10 19:36 ` Jan Kara
2016-11-10 0:00 ` Dave Chinner
2016-11-01 21:08 ` [PATCH 8/8] block: hook up writeback throttling Jens Axboe
2016-11-08 13:42 ` Jan Kara
2016-11-08 15:16 ` Jens Axboe
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=20161102162203.GA7591@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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.