From: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
To: linux-btrace@vger.kernel.org
Subject: [RFC PATCH 06/39] blktrace: add act and prio check helpers
Date: Tue, 25 Aug 2020 22:09:36 +0000 [thread overview]
Message-ID: <20200825221009.6457-7-chaitanya.kulkarni@wdc.com> (raw)
Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
---
kernel/trace/blktrace.c | 37 +++++++++++++++++++++++++++++++++++++
1 file changed, 37 insertions(+)
diff --git a/kernel/trace/blktrace.c b/kernel/trace/blktrace.c
index f739a1b73a47..a2270818e29c 100644
--- a/kernel/trace/blktrace.c
+++ b/kernel/trace/blktrace.c
@@ -311,6 +311,43 @@ static int act_log_check(struct blk_trace *bt, u32 what, sector_t sector,
return 0;
}
+static inline bool prio_log_check(struct blk_trace_ext *bt, u32 ioprio)
+{
+ bool ret;
+
+ switch (IOPRIO_PRIO_CLASS(ioprio)) {
+ case IOPRIO_CLASS_NONE:
+ ret = (bt->prio_mask & 0x01) ? true : false;
+ break;
+ case IOPRIO_CLASS_RT:
+ ret = (bt->prio_mask & 0x02) ? true : false;
+ break;
+ case IOPRIO_CLASS_BE:
+ ret = (bt->prio_mask & 0x04) ? true : false;
+ break;
+ case IOPRIO_CLASS_IDLE:
+ ret = (bt->prio_mask & 0x08) ? true : false;
+ break;
+ default:
+ /*XXX: print rate limit warn here */
+ ret = false;
+ }
+ return ret;
+}
+
+static inline int act_log_check_ext(struct blk_trace_ext *bt, u64 what,
+ sector_t sector, pid_t pid)
+{
+ if (((bt->act_mask << BLK_TC_SHIFT_EXT) & what) = 0)
+ return 1;
+ if (sector && (sector < bt->start_lba || sector > bt->end_lba))
+ return 1;
+ if (bt->pid && pid != bt->pid)
+ return 1;
+
+ return 0;
+}
+
/*
* Data direction bit lookup
*/
--
2.22.1
next reply other threads:[~2020-08-25 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 22:09 Chaitanya Kulkarni [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-05 2:40 [RFC PATCH 06/39] blktrace: add act and prio check helpers Chaitanya Kulkarni
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=20200825221009.6457-7-chaitanya.kulkarni@wdc.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=linux-btrace@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).