[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1485363041.2029.26.camel@hpe.com>
Date: Wed, 25 Jan 2017 15:55:14 +0000
From: "Kani, Toshimitsu" <toshi.kani@....com>
To: "hch@...radead.org" <hch@...radead.org>,
"jmoyer@...hat.com" <jmoyer@...hat.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nvdimm@...1.01.org" <linux-nvdimm@...1.01.org>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"dan.j.williams@...el.com" <dan.j.williams@...el.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"joe@...ches.com" <joe@...ches.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"david@...morbit.com" <david@...morbit.com>
Subject: Re: [PATCH v5] DAX: enable iostat for read/write
On Wed, 2017-01-25 at 10:15 -0500, Jeff Moyer wrote:
> Christoph Hellwig <hch@...radead.org> writes:
>
> > 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.
>
> Agreed, this is a layering violation.
I will check to see if it can fit on top of Dan's patch-set.
Thanks,
-Toshi
Powered by blists - more mailing lists