All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Toshi Kani <toshi.kani@hpe.com>
Cc: linux-nvdimm@lists.01.org, david@fromorbit.com,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	viro@zeniv.linux.org.uk, Joe Perches <joe@perches.com>,
	akpm@linux-foundation.org
Subject: Re: [PATCH v5] DAX: enable iostat for read/write
Date: Wed, 25 Jan 2017 03:19:52 -0800	[thread overview]
Message-ID: <20170125111952.GA11978@infradead.org> (raw)
In-Reply-To: <20170112183848.23159-1-toshi.kani@hpe.com>

On Thu, Jan 12, 2017 at 11:38:48AM -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.
> 
> 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.

NAK.  DAX I/O should not be accounted for block device statistics.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Toshi Kani <toshi.kani@hpe.com>
Cc: akpm@linux-foundation.org, dan.j.williams@intel.com,
	linux-nvdimm@ml01.01.org, david@fromorbit.com,
	linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v5] DAX: enable iostat for read/write
Date: Wed, 25 Jan 2017 03:19:52 -0800	[thread overview]
Message-ID: <20170125111952.GA11978@infradead.org> (raw)
In-Reply-To: <20170112183848.23159-1-toshi.kani@hpe.com>

On Thu, Jan 12, 2017 at 11:38:48AM -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.
> 
> 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.

NAK.  DAX I/O should not be accounted for block device statistics.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Toshi Kani <toshi.kani@hpe.com>
Cc: akpm@linux-foundation.org, dan.j.williams@intel.com,
	linux-nvdimm@lists.01.org, david@fromorbit.com,
	linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v5] DAX: enable iostat for read/write
Date: Wed, 25 Jan 2017 03:19:52 -0800	[thread overview]
Message-ID: <20170125111952.GA11978@infradead.org> (raw)
In-Reply-To: <20170112183848.23159-1-toshi.kani@hpe.com>

On Thu, Jan 12, 2017 at 11:38:48AM -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.
> 
> 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.

NAK.  DAX I/O should not be accounted for block device statistics.

  parent reply	other threads:[~2017-01-25 11:19 UTC|newest]

Thread overview: 14+ 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:38 ` Toshi Kani
2017-01-12 18:38 ` Toshi Kani
2017-01-12 18:02 ` Joe Perches
2017-01-12 18:02   ` Joe Perches
2017-01-12 18:02   ` Joe Perches
2017-01-12 18:26   ` Kani, Toshimitsu
2017-01-12 18:26     ` Kani, Toshimitsu
2017-01-12 18:26     ` Kani, Toshimitsu
2017-01-25 11:19 ` Christoph Hellwig [this message]
2017-01-25 11:19   ` Christoph Hellwig
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=20170125111952.GA11978@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=joe@perches.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 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.