All of lore.kernel.org
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: toshi.kani@hpe.com, dan.j.williams@intel.com,
	david@fromorbit.com, hch@infradead.org, jmoyer@redhat.com,
	joe@perches.com, ross.zwisler@linux.intel.com,
	viro@zeniv.linux.org.uk, mm-commits@vger.kernel.org
Subject: [nacked] dax-enable-iostat-for-read-write.patch removed from -mm tree
Date: Wed, 25 Jan 2017 15:45:49 -0800	[thread overview]
Message-ID: <588938ad.E1VAdLz5Ato5l3q9%akpm@linux-foundation.org> (raw)


The patch titled
     Subject: DAX: enable iostat for read/write
has been removed from the -mm tree.  Its filename was
     dax-enable-iostat-for-read-write.patch

This patch was dropped because it was nacked

------------------------------------------------------
From: Toshi Kani <toshi.kani@hpe.com>
Subject: DAX: enable iostat for read/write

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.

[akpm@linux-foundation.org: make do_acct a bool]
Link: http://lkml.kernel.org/r/20170113233418.32252-1-toshi.kani@hpe.com
Signed-off-by: Toshi Kani <toshi.kani@hpe.com>
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Dave Chinner <david@fromorbit.com>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: Joe Perches <joe@perches.com>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Jeff Moyer <jmoyer@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 fs/dax.c |   15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff -puN fs/dax.c~dax-enable-iostat-for-read-write fs/dax.c
--- a/fs/dax.c~dax-enable-iostat-for-read-write
+++ a/fs/dax.c
@@ -1081,12 +1081,24 @@ dax_iomap_rw(struct kiocb *iocb, struct
 {
 	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;
+	bool do_acct = blk_queue_io_stat(disk->queue);
 
 	if (iov_iter_rw(iter) == WRITE)
 		flags |= IOMAP_WRITE;
 
+	if (do_acct) {
+		size_t sec = iov_iter_count(iter) >> 9;
+
+		start = jiffies;
+		generic_start_io_acct(iov_iter_rw(iter),
+				      max_t(unsigned long, 1, sec),
+				      &disk->part0);
+	}
+
 	while (iov_iter_count(iter)) {
 		ret = iomap_apply(inode, pos, iov_iter_count(iter), flags, ops,
 				iter, dax_iomap_actor);
@@ -1096,6 +1108,9 @@ dax_iomap_rw(struct kiocb *iocb, struct
 		done += ret;
 	}
 
+	if (do_acct)
+		generic_end_io_acct(iov_iter_rw(iter), &disk->part0, start);
+
 	iocb->ki_pos += done;
 	return done ? done : ret;
 }
_

Patches currently in -mm which might be from toshi.kani@hpe.com are



                 reply	other threads:[~2017-01-25 23:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=588938ad.E1VAdLz5Ato5l3q9%akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=jmoyer@redhat.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.