From: Joe Perches <joe@perches.com>
To: Toshi Kani <toshi.kani@hpe.com>,
akpm@linux-foundation.org, dan.j.williams@intel.com
Cc: david@fromorbit.com, viro@zeniv.linux.org.uk,
ross.zwisler@linux.intel.com, linux-nvdimm@ml01.01.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] DAX: enable iostat for read/write
Date: Thu, 12 Jan 2017 10:02:21 -0800 [thread overview]
Message-ID: <1484244141.3065.20.camel@perches.com> (raw)
In-Reply-To: <20170112183848.23159-1-toshi.kani@hpe.com>
On Thu, 2017-01-12 at 11:38 -0700, Toshi Kani wrote:
> DAX IO path does not support iostat, but its metadata IO path does.
> Therefore, iostat shows metadata IO statistics only, which has been
> confusing to users.
[]
> diff --git a/fs/dax.c b/fs/dax.c
[]
> @@ -1058,12 +1058,24 @@ dax_iomap_rw(struct kiocb *iocb, struct iov_iter *iter,
> {
> struct address_space *mapping = iocb->ki_filp->f_mapping;
> struct inode *inode = mapping->host;
> + struct gendisk *disk = inode->i_sb->s_bdev->bd_disk;
> loff_t pos = iocb->ki_pos, ret = 0, done = 0;
> unsigned flags = 0;
> + unsigned long start = 0;
> + int do_acct = blk_queue_io_stat(disk->queue);
>
> if (iov_iter_rw(iter) == WRITE)
> flags |= IOMAP_WRITE;
>
> + if (do_acct) {
> + sector_t sec = iov_iter_count(iter) >> 9;
> +
> + start = jiffies;
> + generic_start_io_acct(iov_iter_rw(iter),
> + min_t(unsigned long, 1, sec),
I believe I mislead you with a thinko.
Your original code was
(!sec) ? 1 : sec
and I suggested incorrectly using min_t
It should of course be max_t. Sorry.
Also, as sec is now sector_t (u64), perhaps this
unsigned long cast is incorrect.
next prev parent reply other threads:[~2017-01-12 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 18:38 [PATCH v5] DAX: enable iostat for read/write Toshi Kani
2017-01-12 18:02 ` Joe Perches [this message]
2017-01-12 18:26 ` Kani, Toshimitsu
2017-01-25 11:19 ` Christoph Hellwig
2017-01-25 15:15 ` Jeff Moyer
2017-01-25 15:55 ` Kani, Toshimitsu
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=1484244141.3065.20.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=toshi.kani@hpe.com \
--cc=viro@zeniv.linux.org.uk \
/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