From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Toshi Kani <toshi.kani@hpe.com>
Cc: akpm@linux-foundation.org, dan.j.williams@intel.com,
viro@zeniv.linux.org.uk, ross.zwisler@linux.intel.com,
linux-nvdimm@lists.01.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] DAX: enable iostat for read/write
Date: Mon, 17 Oct 2016 11:29:57 -0600 [thread overview]
Message-ID: <20161017172957.GC25175@linux.intel.com> (raw)
In-Reply-To: <1476724738-19133-1-git-send-email-toshi.kani@hpe.com>
On Mon, Oct 17, 2016 at 11:18:58AM -0600, 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.
>
> Add iostat support to the DAX read/write path.
>
> Note, iostat still does not support the DAX mmap path as it allows
> user applications to access directly.
>
> Signed-off-by: Toshi Kani <toshi.kani@hpe.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
> ---
> v2:
> - Set a minimum of one sector (Dan Williams)
What about Dave's feedback that this code just reimplements
generic_start_io_acct() and generic_end_io_acct()?
> ---
> fs/dax.c | 37 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 37 insertions(+)
>
> diff --git a/fs/dax.c b/fs/dax.c
> index 014defd..43e5e7a 100644
> --- a/fs/dax.c
> +++ b/fs/dax.c
> @@ -144,6 +144,34 @@ static sector_t to_sector(const struct buffer_head *bh,
> return sector;
> }
>
> +static void dax_iostat_start(struct gendisk *disk, struct iov_iter *iter,
> + unsigned long *start)
> +{
> + int rw = iov_iter_rw(iter);
> + int sec = iov_iter_count(iter) >> 9;
> + int cpu = part_stat_lock();
> +
> + *start = jiffies;
> + part_round_stats(cpu, &disk->part0);
> + part_stat_inc(cpu, &disk->part0, ios[rw]);
> + part_stat_add(cpu, &disk->part0, sectors[rw], ((!sec) ? 1 : sec));
> + part_inc_in_flight(&disk->part0, rw);
> + part_stat_unlock();
> +}
> +
> +static void dax_iostat_end(struct gendisk *disk, struct iov_iter *iter,
> + unsigned long start)
> +{
> + unsigned long duration = jiffies - start;
> + int rw = iov_iter_rw(iter);
> + int cpu = part_stat_lock();
> +
> + part_stat_add(cpu, &disk->part0, ticks[rw], duration);
> + part_round_stats(cpu, &disk->part0);
> + part_dec_in_flight(&disk->part0, rw);
> + part_stat_unlock();
> +}
> +
> static ssize_t dax_io(struct inode *inode, struct iov_iter *iter,
> loff_t start, loff_t end, get_block_t get_block,
> struct buffer_head *bh)
> @@ -265,9 +293,12 @@ ssize_t dax_do_io(struct kiocb *iocb, struct inode *inode,
> ssize_t retval = -EINVAL;
> loff_t pos = iocb->ki_pos;
> loff_t end = pos + iov_iter_count(iter);
> + struct gendisk *disk;
> + unsigned long start = 0;
>
> memset(&bh, 0, sizeof(bh));
> bh.b_bdev = inode->i_sb->s_bdev;
> + disk = bh.b_bdev->bd_disk;
>
> if ((flags & DIO_LOCKING) && iov_iter_rw(iter) == READ)
> inode_lock(inode);
> @@ -276,8 +307,14 @@ ssize_t dax_do_io(struct kiocb *iocb, struct inode *inode,
> if (!(flags & DIO_SKIP_DIO_COUNT))
> inode_dio_begin(inode);
>
> + if (blk_queue_io_stat(disk->queue))
> + dax_iostat_start(disk, iter, &start);
> +
> retval = dax_io(inode, iter, pos, end, get_block, &bh);
>
> + if (start)
> + dax_iostat_end(disk, iter, start);
> +
> if ((flags & DIO_LOCKING) && iov_iter_rw(iter) == READ)
> inode_unlock(inode);
>
next prev parent reply other threads:[~2016-10-17 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 17:18 [PATCH v2] DAX: enable iostat for read/write Toshi Kani
2016-10-17 17:29 ` Ross Zwisler [this message]
2016-10-17 17:45 ` 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=20161017172957.GC25175@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--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;
as well as URLs for NNTP newsgroup(s).