From: Tianxianting <tian.xianting@h3c.com>
To: Jens Axboe <axboe@kernel.dk>, "ast@kernel.org" <ast@kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"kafai@fb.com" <kafai@fb.com>,
"songliubraving@fb.com" <songliubraving@fb.com>,
"yhs@fb.com" <yhs@fb.com>, "andriin@fb.com" <andriin@fb.com>,
"john.fastabend@gmail.com" <john.fastabend@gmail.com>,
"kpsingh@chromium.org" <kpsingh@chromium.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] blk-mq: use BLK_MQ_NO_TAG for no tag
Date: Mon, 24 Aug 2020 06:18:33 +0000 [thread overview]
Message-ID: <19b0d8969dde4e20b1e6a076e48ba716@h3c.com> (raw)
In-Reply-To: <1b85d18e-b0ae-a925-bb84-0a1eb8942099@kernel.dk>
Hi Jens
Sorry to trouble you, I am very sorry for taking it for granted for the patch compile.
I checked, compile for the two changed files are OK:
block/blk-core.c
block/blk-mq-sched.c
Compile failed for the function in below header file:
include/linux/blk-mq.h: request_to_qc_t()
- if (rq->tag != -1)
+ if (rq->tag != BLK_MQ_NO_TAG)
BLK_MQ_NO_TAG is defined in 'block/blk-mq-tag.h', if I include this header file in 'include/linux/blk-mq.h' via '#include "../../block/blk-mq-tag.h"',
Many other similar compile failed happen, for example:
In file included from ./include/linux/../../block/blk-mq-tag.h:5:0,
from ./include/linux/blk-mq.h:8,
from block/blk.h:6,
from block/bio.c:24:
./include/linux/../../block/blk-mq.h:21:29: error: ‘HCTX_MAX_TYPES’ undeclared here (not in a function); did you mean ‘KOBJ_NS_TYPES’?
struct list_head rq_lists[HCTX_MAX_TYPES];
^~~~~~~~~~~~~~
If I moved below BLK_MQ_NO_TAG definition to 'include/linux/blk-mq.h', all kernel compiles are ok with the patch.
enum {
BLK_MQ_NO_TAG = -1U,
BLK_MQ_TAG_MIN = 1,
BLK_MQ_TAG_MAX = BLK_MQ_NO_TAG - 1,
};
Will you accept above moving of BLK_MQ_NO_TAG to 'include/linux/blk-mq.h'?
Thanks
-----Original Message-----
From: Jens Axboe [mailto:axboe@kernel.dk]
Sent: Monday, August 24, 2020 4:58 AM
To: tianxianting (RD) <tian.xianting@h3c.com>; ast@kernel.org; daniel@iogearbox.net; kafai@fb.com; songliubraving@fb.com; yhs@fb.com; andriin@fb.com; john.fastabend@gmail.com; kpsingh@chromium.org
Cc: linux-block@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blk-mq: use BLK_MQ_NO_TAG for no tag
On 8/23/20 9:44 AM, Xianting Tian wrote:
> Replace various magic -1 constants for tags with BLK_MQ_NO_TAG.
Doesn't look like this patch was even compiled...
--
Jens Axboe
next prev parent reply other threads:[~2020-08-24 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 15:44 [PATCH] blk-mq: use BLK_MQ_NO_TAG for no tag Xianting Tian
2020-08-23 19:44 ` kernel test robot
2020-08-23 20:56 ` kernel test robot
2020-08-23 20:58 ` Jens Axboe
2020-08-24 6:18 ` Tianxianting [this message]
2020-08-24 1:04 ` kernel test robot
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=19b0d8969dde4e20b1e6a076e48ba716@h3c.com \
--to=tian.xianting@h3c.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox