From: Keith Busch <keith.busch@intel.com>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-nvme@lists.infradead.org,
jack@suse.com, david@fromorbit.com, tytso@mit.edu,
prakash.v@samsung.com
Subject: Re: [PATCH v2 0/4] Write-hint for FS journal
Date: Fri, 25 Jan 2019 09:23:53 -0700 [thread overview]
Message-ID: <20190125162353.GA11210@localhost.localdomain> (raw)
In-Reply-To: <1547047861-7271-1-git-send-email-joshi.k@samsung.com>
On Wed, Jan 09, 2019 at 09:00:57PM +0530, Kanchan Joshi wrote:
> Towards supporing write-hints/streams for filesystem journal.
>
> Here is the v1 patch for background -
> https://marc.info/?l=linux-fsdevel&m=154444637519020&w=2
>
> Changes since v1:
> - introduce four more hints for in-kernel use, as recommended by Dave chinner
> & Jens axboe. This isolates kernel-mode hints from user-mode ones.
The nvme driver disables streams if the controller doesn't support
BLK_MAX_WRITE_HINT number of streams, so this series breaks the feature
for controllers that only support up to 4.
WARNING: multiple messages have this Message-ID (diff)
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH v2 0/4] Write-hint for FS journal
Date: Fri, 25 Jan 2019 09:23:53 -0700 [thread overview]
Message-ID: <20190125162353.GA11210@localhost.localdomain> (raw)
In-Reply-To: <1547047861-7271-1-git-send-email-joshi.k@samsung.com>
On Wed, Jan 09, 2019@09:00:57PM +0530, Kanchan Joshi wrote:
> Towards supporing write-hints/streams for filesystem journal.
>
> Here is the v1 patch for background -
> https://marc.info/?l=linux-fsdevel&m=154444637519020&w=2
>
> Changes since v1:
> - introduce four more hints for in-kernel use, as recommended by Dave chinner
> & Jens axboe. This isolates kernel-mode hints from user-mode ones.
The nvme driver disables streams if the controller doesn't support
BLK_MAX_WRITE_HINT number of streams, so this series breaks the feature
for controllers that only support up to 4.
next prev parent reply other threads:[~2019-01-25 16:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190109153328epcas2p4643cbdc7a2182b47893a2bcaa0778e17@epcas2p4.samsung.com>
2019-01-09 15:30 ` [PATCH v2 0/4] Write-hint for FS journal Kanchan Joshi
2019-01-09 15:30 ` Kanchan Joshi
2019-01-09 15:30 ` [PATCH 1/4] block: Increase count of supported write-hints Kanchan Joshi
2019-01-09 15:30 ` Kanchan Joshi
2019-01-09 15:30 ` [PATCH 2/4] fs: introduce four macros for in-kernel hints Kanchan Joshi
2019-01-09 15:30 ` Kanchan Joshi
2019-01-23 18:27 ` [PATCH 2/4] " Javier González
2019-01-23 18:27 ` Javier González
2019-01-24 8:35 ` Jan Kara
2019-01-24 8:35 ` Jan Kara
2019-01-24 9:23 ` Javier González
2019-01-24 9:23 ` Javier González
2019-01-09 15:31 ` [PATCH 3/4] fs: introduce APIs to enable sending write-hint with buffer-head Kanchan Joshi
2019-01-09 15:31 ` Kanchan Joshi
2019-01-09 15:31 ` [PATCH 4/4] fs/ext4,jbd2: add support for passing write-hint with journal Kanchan Joshi
2019-01-09 15:31 ` Kanchan Joshi
2019-01-24 8:50 ` Jan Kara
2019-01-24 8:50 ` Jan Kara
2019-01-23 18:35 ` [PATCH v2 0/4] Write-hint for FS journal Javier González
2019-01-23 18:35 ` Javier González
2019-01-24 8:29 ` Jan Kara
2019-01-24 8:29 ` Jan Kara
2019-01-25 14:20 ` Kanchan Joshi
2019-01-25 14:20 ` Kanchan Joshi
2019-01-25 16:23 ` Keith Busch [this message]
2019-01-25 16:23 ` Keith Busch
2019-01-28 12:47 ` Jan Kara
2019-01-28 12:47 ` Jan Kara
2019-01-28 23:24 ` Keith Busch
2019-01-28 23:24 ` Keith Busch
2019-01-29 10:07 ` Jan Kara
2019-01-29 10:07 ` Jan Kara
2019-01-30 0:13 ` Dave Chinner
2019-01-30 0:13 ` Dave Chinner
2019-01-30 13:54 ` Kanchan Joshi
2019-01-30 13:54 ` Kanchan Joshi
2019-02-05 11:50 ` Jan Kara
2019-02-05 11:50 ` Jan Kara
2019-02-05 22:53 ` Dave Chinner
2019-02-05 22:53 ` Dave Chinner
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=20190125162353.GA11210@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=david@fromorbit.com \
--cc=jack@suse.com \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=prakash.v@samsung.com \
--cc=tytso@mit.edu \
/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.