From: Kanchan Joshi <joshi.k@samsung.com> To: linux-fsdevel@vger.kernel.org Cc: 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, Kanchan Joshi <joshi.k@samsung.com> Subject: [PATCH 1/4] block: Increase count of supported write-hints Date: Wed, 09 Jan 2019 21:00:58 +0530 [thread overview] Message-ID: <1547047861-7271-2-git-send-email-joshi.k@samsung.com> (raw) In-Reply-To: <1547047861-7271-1-git-send-email-joshi.k@samsung.com> This patch bumps up write-hint count to support four new, in-kernel hints. Signed-off-by: Kanchan Joshi <joshi.k@samsung.com> --- include/linux/blkdev.h | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h index 338604d..df07759 100644 --- a/include/linux/blkdev.h +++ b/include/linux/blkdev.h @@ -568,7 +568,10 @@ struct request_queue { struct work_struct release_work; -#define BLK_MAX_WRITE_HINTS 5 +#define BLK_MAX_USER_WRITE_HINTS 5 +#define BLK_MAX_KERNEL_WRITE_HINTS 4 +#define BLK_MAX_WRITE_HINTS (BLK_MAX_USER_WRITE_HINTS + \ + BLK_MAX_KERNEL_WRITE_HINTS) u64 write_hints[BLK_MAX_WRITE_HINTS]; }; -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: joshi.k@samsung.com (Kanchan Joshi) Subject: [PATCH 1/4] block: Increase count of supported write-hints Date: Wed, 09 Jan 2019 21:00:58 +0530 [thread overview] Message-ID: <1547047861-7271-2-git-send-email-joshi.k@samsung.com> (raw) In-Reply-To: <1547047861-7271-1-git-send-email-joshi.k@samsung.com> This patch bumps up write-hint count to support four new, in-kernel hints. Signed-off-by: Kanchan Joshi <joshi.k at samsung.com> --- include/linux/blkdev.h | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h index 338604d..df07759 100644 --- a/include/linux/blkdev.h +++ b/include/linux/blkdev.h @@ -568,7 +568,10 @@ struct request_queue { struct work_struct release_work; -#define BLK_MAX_WRITE_HINTS 5 +#define BLK_MAX_USER_WRITE_HINTS 5 +#define BLK_MAX_KERNEL_WRITE_HINTS 4 +#define BLK_MAX_WRITE_HINTS (BLK_MAX_USER_WRITE_HINTS + \ + BLK_MAX_KERNEL_WRITE_HINTS) u64 write_hints[BLK_MAX_WRITE_HINTS]; }; -- 2.7.4
next prev parent reply other threads:[~2019-01-09 15:33 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 [not found] ` <CGME20190109153332epcas1p187b419176a8d1d0be4982a275c0b9e86@epcas1p1.samsung.com> 2019-01-09 15:30 ` Kanchan Joshi [this message] 2019-01-09 15:30 ` [PATCH 1/4] block: Increase count of supported write-hints Kanchan Joshi [not found] ` <CGME20190109153336epcas2p29b3275b6c545e483a3f43b92268f08bf@epcas2p2.samsung.com> 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 [not found] ` <CGME20190109153339epcas2p4691a898dde0174a7565d62fcb3be0b6d@epcas2p4.samsung.com> 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 [not found] ` <CGME20190109153342epcas2p3208f62a4dd876f8e1765b48f8aec2432@epcas2p3.samsung.com> 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 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=1547047861-7271-2-git-send-email-joshi.k@samsung.com \ --to=joshi.k@samsung.com \ --cc=david@fromorbit.com \ --cc=jack@suse.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: linkBe 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.