From: Dan Williams <dan.j.williams@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: dm-devel@redhat.com, Matthew Wilcox <mawilcox@microsoft.com>,
X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3 13/14] filesystem-dax: gate calls to dax_flush() on QUEUE_FLAG_WC
Date: Wed, 14 Jun 2017 09:49:50 -0700 [thread overview]
Message-ID: <CAPcyv4iexm8MAnie0s_5VS23h4FtQdBTV7ho47jynWSr1HdfAA@mail.gmail.com> (raw)
In-Reply-To: <20170614104626.GA21506@quack2.suse.cz>
On Wed, Jun 14, 2017 at 3:46 AM, Jan Kara <jack@suse.cz> wrote:
> On Fri 09-06-17 13:24:56, Dan Williams wrote:
>> Some platforms arrange for cpu caches to be flushed on power-fail. On
>> those platforms there is no requirement that the kernel track and flush
>> potentially dirty cache lines. Given that we still insert entries into
>> the radix for locking purposes this patch only disables the cache flush
>> loop, not the dirty tracking.
>>
>> Userspace can override the default cache setting via the block device
>> queue "write_cache" attribute in sysfs.
>>
>> Cc: Jan Kara <jack@suse.cz>
>> Cc: Jeff Moyer <jmoyer@redhat.com>
>> Cc: Christoph Hellwig <hch@lst.de>
>> Cc: Matthew Wilcox <mawilcox@microsoft.com>
>> Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
>> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
>
> ...
>
>> - dax_flush(dax_dev, pgoff, kaddr, size);
>> + if (test_bit(QUEUE_FLAG_WC, &bdev->bd_queue->queue_flags))
>> + dax_flush(dax_dev, pgoff, kaddr, size);
>
> IMHO the check belongs into dax_flush() similarly as blkdev_issue_flush()
> takes silently handles whether the flush is actually needed or not.
Looks good, will do.
_______________________________________________
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: Dan Williams <dan.j.williams@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
dm-devel@redhat.com, Matthew Wilcox <mawilcox@microsoft.com>,
X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jeff Moyer <jmoyer@redhat.com>, Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3 13/14] filesystem-dax: gate calls to dax_flush() on QUEUE_FLAG_WC
Date: Wed, 14 Jun 2017 09:49:50 -0700 [thread overview]
Message-ID: <CAPcyv4iexm8MAnie0s_5VS23h4FtQdBTV7ho47jynWSr1HdfAA@mail.gmail.com> (raw)
In-Reply-To: <20170614104626.GA21506@quack2.suse.cz>
On Wed, Jun 14, 2017 at 3:46 AM, Jan Kara <jack@suse.cz> wrote:
> On Fri 09-06-17 13:24:56, Dan Williams wrote:
>> Some platforms arrange for cpu caches to be flushed on power-fail. On
>> those platforms there is no requirement that the kernel track and flush
>> potentially dirty cache lines. Given that we still insert entries into
>> the radix for locking purposes this patch only disables the cache flush
>> loop, not the dirty tracking.
>>
>> Userspace can override the default cache setting via the block device
>> queue "write_cache" attribute in sysfs.
>>
>> Cc: Jan Kara <jack@suse.cz>
>> Cc: Jeff Moyer <jmoyer@redhat.com>
>> Cc: Christoph Hellwig <hch@lst.de>
>> Cc: Matthew Wilcox <mawilcox@microsoft.com>
>> Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
>> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
>
> ...
>
>> - dax_flush(dax_dev, pgoff, kaddr, size);
>> + if (test_bit(QUEUE_FLAG_WC, &bdev->bd_queue->queue_flags))
>> + dax_flush(dax_dev, pgoff, kaddr, size);
>
> IMHO the check belongs into dax_flush() similarly as blkdev_issue_flush()
> takes silently handles whether the flush is actually needed or not.
Looks good, will do.
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>
Cc: dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Matthew Wilcox <mawilcox-0li6OtcxBFHby3iVrkZq2A@public.gmane.org>,
X86 ML <x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org"
<linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>,
Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
linux-fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Subject: Re: [PATCH v3 13/14] filesystem-dax: gate calls to dax_flush() on QUEUE_FLAG_WC
Date: Wed, 14 Jun 2017 09:49:50 -0700 [thread overview]
Message-ID: <CAPcyv4iexm8MAnie0s_5VS23h4FtQdBTV7ho47jynWSr1HdfAA@mail.gmail.com> (raw)
In-Reply-To: <20170614104626.GA21506-4I4JzKEfoa/jFM9bn6wA6Q@public.gmane.org>
On Wed, Jun 14, 2017 at 3:46 AM, Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org> wrote:
> On Fri 09-06-17 13:24:56, Dan Williams wrote:
>> Some platforms arrange for cpu caches to be flushed on power-fail. On
>> those platforms there is no requirement that the kernel track and flush
>> potentially dirty cache lines. Given that we still insert entries into
>> the radix for locking purposes this patch only disables the cache flush
>> loop, not the dirty tracking.
>>
>> Userspace can override the default cache setting via the block device
>> queue "write_cache" attribute in sysfs.
>>
>> Cc: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>
>> Cc: Jeff Moyer <jmoyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>> Cc: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
>> Cc: Matthew Wilcox <mawilcox-0li6OtcxBFHby3iVrkZq2A@public.gmane.org>
>> Cc: Ross Zwisler <ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
>> Signed-off-by: Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>
> ...
>
>> - dax_flush(dax_dev, pgoff, kaddr, size);
>> + if (test_bit(QUEUE_FLAG_WC, &bdev->bd_queue->queue_flags))
>> + dax_flush(dax_dev, pgoff, kaddr, size);
>
> IMHO the check belongs into dax_flush() similarly as blkdev_issue_flush()
> takes silently handles whether the flush is actually needed or not.
Looks good, will do.
next prev parent reply other threads:[~2017-06-14 16:48 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 20:23 [PATCH v3 00/14] pmem: stop abusing __copy_user_nocache(), and other reworks Dan Williams
2017-06-09 20:23 ` Dan Williams
2017-06-09 20:23 ` Dan Williams
2017-06-09 20:23 ` [PATCH v3 01/14] x86, uaccess: introduce copy_from_iter_flushcache for pmem / cache-bypass operations Dan Williams
2017-06-09 20:23 ` Dan Williams
2017-06-09 20:23 ` Dan Williams
2017-06-18 8:28 ` Christoph Hellwig
2017-06-18 8:28 ` Christoph Hellwig
2017-06-18 8:28 ` Christoph Hellwig
2017-06-19 2:02 ` Dan Williams
2017-06-19 2:02 ` Dan Williams
2017-06-19 2:02 ` Dan Williams
2017-06-09 20:23 ` [PATCH v3 02/14] dm: add ->copy_from_iter() dax operation support Dan Williams
2017-06-09 20:23 ` Dan Williams
2017-06-09 20:23 ` Dan Williams
2017-06-15 0:46 ` Kani, Toshimitsu
2017-06-15 0:46 ` Kani, Toshimitsu
2017-06-15 0:46 ` Kani, Toshimitsu
2017-06-15 1:21 ` Kani, Toshimitsu
2017-06-15 1:21 ` Kani, Toshimitsu
2017-06-18 8:37 ` Christoph Hellwig
2017-06-18 8:37 ` Christoph Hellwig
2017-06-18 8:37 ` Christoph Hellwig
2017-06-19 2:04 ` Dan Williams
2017-06-19 2:04 ` Dan Williams
2017-06-19 2:04 ` Dan Williams
2017-06-09 20:24 ` [PATCH v3 03/14] filesystem-dax: convert to dax_copy_from_iter() Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-14 10:58 ` Jan Kara
2017-06-14 10:58 ` Jan Kara
2017-06-14 10:58 ` Jan Kara
2017-06-09 20:24 ` [PATCH v3 04/14] dax, pmem: introduce an optional 'flush' dax_operation Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-14 10:57 ` Jan Kara
2017-06-14 10:57 ` Jan Kara
2017-06-14 10:57 ` Jan Kara
2017-06-09 20:24 ` [PATCH v3 05/14] dm: add ->flush() dax operation support Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-15 1:44 ` Kani, Toshimitsu
2017-06-15 1:44 ` Kani, Toshimitsu
2017-06-15 1:44 ` Kani, Toshimitsu
2017-06-09 20:24 ` [PATCH v3 06/14] filesystem-dax: convert to dax_flush() Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-14 10:56 ` Jan Kara
2017-06-14 10:56 ` Jan Kara
2017-06-14 10:56 ` Jan Kara
2017-06-09 20:24 ` [PATCH v3 07/14] x86, dax: replace clear_pmem() with open coded memset + dax_ops->flush Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-14 10:55 ` Jan Kara
2017-06-14 10:55 ` Jan Kara
2017-06-14 10:55 ` Jan Kara
2017-06-09 20:24 ` [PATCH v3 08/14] x86, dax, libnvdimm: move wb_cache_pmem() to libnvdimm Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-12 0:29 ` [PATCH v4 " Dan Williams
2017-06-12 0:29 ` Dan Williams
2017-06-14 10:54 ` [PATCH v3 " Jan Kara
2017-06-14 10:54 ` Jan Kara
2017-06-14 16:49 ` Dan Williams
2017-06-14 16:49 ` Dan Williams
2017-06-14 16:49 ` Dan Williams
2017-06-15 8:11 ` Jan Kara
2017-06-15 8:11 ` Jan Kara
2017-06-15 8:11 ` Jan Kara
2017-06-18 8:40 ` Christoph Hellwig
2017-06-18 8:40 ` Christoph Hellwig
2017-06-18 8:40 ` Christoph Hellwig
2017-06-19 2:06 ` Dan Williams
2017-06-19 2:06 ` Dan Williams
2017-06-19 2:06 ` Dan Williams
2017-06-09 20:24 ` [PATCH v3 09/14] x86, libnvdimm, pmem: move arch_invalidate_pmem() " Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-14 10:49 ` Jan Kara
2017-06-14 10:49 ` Jan Kara
2017-06-09 20:24 ` [PATCH v3 10/14] pmem: remove global pmem api Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-14 10:48 ` Jan Kara
2017-06-14 10:48 ` Jan Kara
2017-06-14 10:48 ` Jan Kara
2017-06-09 20:24 ` [PATCH v3 11/14] libnvdimm, pmem: fix persistence warning Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` [PATCH v3 12/14] libnvdimm, nfit: enable support for volatile ranges Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` [PATCH v3 13/14] filesystem-dax: gate calls to dax_flush() on QUEUE_FLAG_WC Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-09 20:24 ` Dan Williams
2017-06-14 10:46 ` Jan Kara
2017-06-14 10:46 ` Jan Kara
2017-06-14 16:49 ` Dan Williams [this message]
2017-06-14 16:49 ` Dan Williams
2017-06-14 16:49 ` Dan Williams
2017-06-14 23:11 ` [PATCH v4 13/14] libnvdimm, pmem: gate cache management on QUEUE_FLAG_WC in pmem_dax_flush() Dan Williams
2017-06-14 23:11 ` Dan Williams
2017-06-15 8:09 ` Jan Kara
2017-06-15 8:09 ` Jan Kara
2017-06-18 8:45 ` [PATCH v3 13/14] filesystem-dax: gate calls to dax_flush() on QUEUE_FLAG_WC Christoph Hellwig
2017-06-18 8:45 ` Christoph Hellwig
2017-06-18 8:45 ` Christoph Hellwig
2017-06-19 2:07 ` Dan Williams
2017-06-19 2:07 ` Dan Williams
2017-06-19 2:07 ` Dan Williams
2017-06-09 20:25 ` [PATCH v3 14/14] libnvdimm, pmem: disable dax flushing when pmem is fronting a volatile region Dan Williams
2017-06-09 20:25 ` Dan Williams
2017-06-09 20:25 ` Dan Williams
2017-06-09 23:21 ` Dan Williams
2017-06-09 23:21 ` Dan Williams
2017-06-10 17:54 ` [PATCH v4 " Dan Williams
2017-06-10 17:54 ` Dan Williams
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=CAPcyv4iexm8MAnie0s_5VS23h4FtQdBTV7ho47jynWSr1HdfAA@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mawilcox@microsoft.com \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.org \
/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.