From: Jens Axboe <jens.axboe@oracle.com>
To: Nikanth Karthikesan <knikanth@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Cleanup: Remove unused __REQ_NR_BITS from enum rq_flag_bits
Date: Mon, 27 Apr 2009 13:46:33 +0200 [thread overview]
Message-ID: <20090427114633.GA4593@kernel.dk> (raw)
In-Reply-To: <200904271705.30550.knikanth@suse.de>
On Mon, Apr 27 2009, Nikanth Karthikesan wrote:
> The __REQ_NR_BITS was being used by blk_dump_rq_flags() long back, while
> printing the individual request flag bits as strings to limit to the used
> bits. But it does not use it now. Remove unused enum.
>
> Signed-off-by: Nikanth Karthikesan <knikanth@suse.de>
>
> ---
>
> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
> index ba54c83..f41abbb 100644
> --- a/include/linux/blkdev.h
> +++ b/include/linux/blkdev.h
> @@ -118,7 +118,6 @@ enum rq_flag_bits {
> __REQ_COPY_USER, /* contains copies of user pages */
> __REQ_INTEGRITY, /* integrity metadata has been remapped */
> __REQ_NOIDLE, /* Don't anticipate more IO after this one */
> - __REQ_NR_BITS, /* stops here */
> };
>
> #define REQ_RW (1 << __REQ_RW)
Lets turn it into something useful instead. It's meant to catch someone
adding too many flags, how about something like this:
Untested ;-)
diff --git a/block/blk-core.c b/block/blk-core.c
index d73eb76..e62ef94 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -2159,6 +2159,8 @@ EXPORT_SYMBOL(kblockd_schedule_work);
int __init blk_dev_init(void)
{
+ BUILD_BUG_ON(__REQ_NR_BITS > 8 * sizeof(int));
+
kblockd_workqueue = create_workqueue("kblockd");
if (!kblockd_workqueue)
panic("Failed to create kblockd\n");
--
Jens Axboe
next prev parent reply other threads:[~2009-04-27 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 11:35 [PATCH] Cleanup: Remove unused __REQ_NR_BITS from enum rq_flag_bits Nikanth Karthikesan
2009-04-27 11:46 ` Jens Axboe [this message]
2009-04-27 12:05 ` Nikanth Karthikesan
2009-04-27 12:11 ` 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=20090427114633.GA4593@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=knikanth@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox