From: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
To: linux-block@vger.kernel.org
Cc: colyli@suse.de, linux-bcache@vger.kernel.org,
linux-btrace@vger.kernel.org, xen-devel@lists.xenproject.org,
kent.overstreet@gmail.com, yuchao0@huawei.com,
jaegeuk@kernel.org, damien.lemoal@wdc.com,
konrad.wilk@oracle.com, roger.pau@citrix.com, bvanassche@acm.org,
linux-scsi@vger.kernel.org,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Subject: [PATCH V5 1/9] block: add a helper function to read nr_setcs
Date: Tue, 20 Aug 2019 23:14:15 -0700 [thread overview]
Message-ID: <20190821061423.3408-2-chaitanya.kulkarni@wdc.com> (raw)
In-Reply-To: <20190821061423.3408-1-chaitanya.kulkarni@wdc.com>
This patch introduces helper function to read the number of sectors
from struct block_device->bd_part member. For more details Please refer
to the comment in the include/linux/genhd.h for part_nr_sects_read().
Reviewed-by: Minwoo Im <minwoo.im.dev@gmail.com>
Reviewed-by: Martin K. Petersen <martin.petersen@xxxxxxxxxx>
Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
---
include/linux/blkdev.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index 4798bb25f1ee..aa5801c8ff73 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -1468,6 +1468,11 @@ static inline void put_dev_sector(Sector p)
put_page(p.v);
}
+static inline sector_t bdev_nr_sects(struct block_device *bdev)
+{
+ return part_nr_sects_read(bdev->bd_part);
+}
+
int kblockd_schedule_work(struct work_struct *work);
int kblockd_schedule_work_on(int cpu, struct work_struct *work);
int kblockd_mod_delayed_work_on(int cpu, struct delayed_work *dwork, unsigned long delay);
--
2.17.0
next prev parent reply other threads:[~2019-08-21 6:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 6:14 [PATCH V5 0/9] block: use right accessor to read nr_sects Chaitanya Kulkarni
2019-08-21 6:14 ` Chaitanya Kulkarni [this message]
2019-08-21 15:18 ` [PATCH V5 1/9] block: add a helper function to read nr_setcs Bart Van Assche
2019-08-21 6:14 ` [PATCH V5 2/9] blk-zoned: update blkdev_nr_zones() with helper Chaitanya Kulkarni
2019-08-21 6:14 ` [PATCH V5 3/9] blk-zoned: update blkdev_report_zone() " Chaitanya Kulkarni
2019-08-21 6:14 ` [PATCH V5 4/9] blk-zoned: update blkdev_reset_zones() " Chaitanya Kulkarni
2019-08-21 6:14 ` [PATCH V5 5/9] bcache: update cached_dev_init() " Chaitanya Kulkarni
2019-08-21 6:14 ` [PATCH V5 6/9] f2fs: use helper in init_blkz_info() Chaitanya Kulkarni
2019-08-21 6:14 ` [PATCH V5 7/9] blktrace: use helper in blk_trace_setup_lba() Chaitanya Kulkarni
2019-08-21 6:14 ` [COMPILE TESTED PATCH V5 8/9] target/pscsi: use helper in pscsi_get_blocks() Chaitanya Kulkarni
2019-08-21 6:14 ` [COMPILE TESTED PATCH V5 9/9] xen/blkback: use helper in vbd_sz() Chaitanya Kulkarni
2019-08-21 15:20 ` [PATCH V5 0/9] block: use right accessor to read nr_sects Bart Van Assche
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=20190821061423.3408-2-chaitanya.kulkarni@wdc.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=bvanassche@acm.org \
--cc=colyli@suse.de \
--cc=damien.lemoal@wdc.com \
--cc=jaegeuk@kernel.org \
--cc=kent.overstreet@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrace@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yuchao0@huawei.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;
as well as URLs for NNTP newsgroup(s).