The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Matias Bjørling" <m@bjorling.me>
To: thornber@redhat.com, snitzer@redhat.com, hch@infradead.org,
	hayakawa@valinux.co.jp, axboe@fb.com, andy@rudoff.com,
	dm-devel@redhat.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, bvanassche@acm.org,
	linux-nvme@lists.infradead.org
Cc: jmad@itu.dk, "Matias Bjørling" <m@bjorling.me>
Subject: [PATCH 2/5] block: extend rq_flag_bits
Date: Wed,  8 Oct 2014 17:55:33 +0200	[thread overview]
Message-ID: <1412783736-18115-3-git-send-email-m@bjorling.me> (raw)
In-Reply-To: <1412783736-18115-1-git-send-email-m@bjorling.me>

From: Jesper Madsen <jmad@itu.dk>

The rq_flag_bits is extended by REQ_NVM and REQ_NVM_MAPPED

REQ_NVM is used to detect request have through LightNVM on submission, and can
be detected on completion.

REQ_NVM_MAPPED is used to detect if request have mapped appropriately through
LightNVM.

The latter is added temponarily to debug the LightNVM key-value target and will
be removed later.

Signed-off-by: Matias Bjørling <m@bjorling.me>
---
 include/linux/blk_types.h | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/include/linux/blk_types.h b/include/linux/blk_types.h
index 66c2167..b1d2f4d 100644
--- a/include/linux/blk_types.h
+++ b/include/linux/blk_types.h
@@ -191,6 +191,8 @@ enum rq_flag_bits {
 	__REQ_END,		/* last of chain of requests */
 	__REQ_HASHED,		/* on IO scheduler merge hash */
 	__REQ_MQ_INFLIGHT,	/* track inflight for MQ */
+	__REQ_NVM,		/* request is queued via lightnvm */
+	__REQ_NVM_MAPPED,	/* lightnvm mapped this request */
 	__REQ_NR_BITS,		/* stops here */
 };
 
@@ -245,5 +247,7 @@ enum rq_flag_bits {
 #define REQ_END			(1ULL << __REQ_END)
 #define REQ_HASHED		(1ULL << __REQ_HASHED)
 #define REQ_MQ_INFLIGHT		(1ULL << __REQ_MQ_INFLIGHT)
+#define REQ_NVM			(1ULL << __REQ_NVM)
+#define REQ_NVM_MAPPED		(1ULL << __REQ_NVM_MAPPED)
 
 #endif /* __LINUX_BLK_TYPES_H */
-- 
1.9.1


  parent reply	other threads:[~2014-10-08 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 15:55 [PATCH 0/5] Support for Open-Channel SSDs (was dm-lightnvm) Matias Bjørling
2014-10-08 15:55 ` [PATCH 1/5] NVMe: Convert to blk-mq Matias Bjørling
2014-10-08 15:55 ` Matias Bjørling [this message]
2014-10-08 15:55 ` [PATCH 3/5] lightnvm: Support for Open-Channel SSDs Matias Bjørling
2014-10-08 15:55 ` [PATCH 4/5] lightnvm: NVMe integration Matias Bjørling
2014-10-08 16:13   ` Keith Busch
2014-10-08 15:55 ` [PATCH 5/5] lightnvm: null_blk integration Matias Bjørling

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=1412783736-18115-3-git-send-email-m@bjorling.me \
    --to=m@bjorling.me \
    --cc=andy@rudoff.com \
    --cc=axboe@fb.com \
    --cc=bvanassche@acm.org \
    --cc=dm-devel@redhat.com \
    --cc=hayakawa@valinux.co.jp \
    --cc=hch@infradead.org \
    --cc=jmad@itu.dk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=snitzer@redhat.com \
    --cc=thornber@redhat.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