From: Dan Williams <dan.j.williams@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Mike Snitzer <msnitzer@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [dm-devel] [PATCH] dm-writecache
Date: Thu, 8 Mar 2018 09:08:32 -0800 [thread overview]
Message-ID: <CAPcyv4gBUt5NYK2Lx0dMZAnENeSgKm3KaUvY9kkqB+PNPyQu4w@mail.gmail.com> (raw)
In-Reply-To: <20180308145153.GB23262@infradead.org>
On Thu, Mar 8, 2018 at 6:51 AM, Christoph Hellwig <hch@infradead.org> wrote:
>> --- /dev/null 1970-01-01 00:00:00.000000000 +0000
>> +++ linux-2.6/drivers/md/dm-writecache.c 2018-03-08 14:23:31.059999000 +0100
>> @@ -0,0 +1,2417 @@
>> +#include <linux/device-mapper.h>
>
> missing copyright statement, or for those new-fashioned SPDX statement.
>
>> +#define WRITEBACK_FUA true
>
> no business having this around.
>
>> +#ifndef bio_set_dev
>> +#define bio_set_dev(bio, dev) ((bio)->bi_bdev = (dev))
>> +#endif
>> +#ifndef timer_setup
>> +#define timer_setup(t, c, f) setup_timer(t, c, (unsigned long)(t))
>> +#endif
>
> no business in mainline.
>
>> +/*
>> + * On X86, non-temporal stores are more efficient than cache flushing.
>> + * On ARM64, cache flushing is more efficient.
>> + */
>> +#if defined(CONFIG_X86_64)
>> +#define NT_STORE(dest, src) \
>> +do { \
>> + typeof(src) val = (src); \
>> + memcpy_flushcache(&(dest), &val, sizeof(src)); \
>> +} while (0)
>> +#define COMMIT_FLUSHED() wmb()
>> +#else
>> +#define NT_STORE(dest, src) WRITE_ONCE(dest, src)
>> +#define FLUSH_RANGE dax_flush
>> +#define COMMIT_FLUSHED() do { } while (0)
>> +#endif
>
> Please use proper APIs for this, this has no business in a driver.
I had the same feedback, and Mikulas sent this useful enhancement to
the memcpy_flushcache API:
https://patchwork.kernel.org/patch/10217655/
...it's in my queue to either push through -tip or add it to the next
libnvdimm pull request for 4.17-rc1.
_______________________________________________
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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: Mike Snitzer <msnitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Mikulas Patocka
<mpatocka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
device-mapper development
<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"Alasdair G. Kergon"
<agk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-nvdimm
<linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
Subject: Re: [dm-devel] [PATCH] dm-writecache
Date: Thu, 8 Mar 2018 09:08:32 -0800 [thread overview]
Message-ID: <CAPcyv4gBUt5NYK2Lx0dMZAnENeSgKm3KaUvY9kkqB+PNPyQu4w@mail.gmail.com> (raw)
In-Reply-To: <20180308145153.GB23262-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
On Thu, Mar 8, 2018 at 6:51 AM, Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> wrote:
>> --- /dev/null 1970-01-01 00:00:00.000000000 +0000
>> +++ linux-2.6/drivers/md/dm-writecache.c 2018-03-08 14:23:31.059999000 +0100
>> @@ -0,0 +1,2417 @@
>> +#include <linux/device-mapper.h>
>
> missing copyright statement, or for those new-fashioned SPDX statement.
>
>> +#define WRITEBACK_FUA true
>
> no business having this around.
>
>> +#ifndef bio_set_dev
>> +#define bio_set_dev(bio, dev) ((bio)->bi_bdev = (dev))
>> +#endif
>> +#ifndef timer_setup
>> +#define timer_setup(t, c, f) setup_timer(t, c, (unsigned long)(t))
>> +#endif
>
> no business in mainline.
>
>> +/*
>> + * On X86, non-temporal stores are more efficient than cache flushing.
>> + * On ARM64, cache flushing is more efficient.
>> + */
>> +#if defined(CONFIG_X86_64)
>> +#define NT_STORE(dest, src) \
>> +do { \
>> + typeof(src) val = (src); \
>> + memcpy_flushcache(&(dest), &val, sizeof(src)); \
>> +} while (0)
>> +#define COMMIT_FLUSHED() wmb()
>> +#else
>> +#define NT_STORE(dest, src) WRITE_ONCE(dest, src)
>> +#define FLUSH_RANGE dax_flush
>> +#define COMMIT_FLUSHED() do { } while (0)
>> +#endif
>
> Please use proper APIs for this, this has no business in a driver.
I had the same feedback, and Mikulas sent this useful enhancement to
the memcpy_flushcache API:
https://patchwork.kernel.org/patch/10217655/
...it's in my queue to either push through -tip or add it to the next
libnvdimm pull request for 4.17-rc1.
next prev parent reply other threads:[~2018-03-08 17:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 13:25 [PATCH] dm-writecache Mikulas Patocka
2018-03-08 14:51 ` [dm-devel] " Christoph Hellwig
2018-03-08 14:51 ` Christoph Hellwig
2018-03-08 17:08 ` Dan Williams [this message]
2018-03-08 17:08 ` Dan Williams
2018-03-12 7:48 ` Christoph Hellwig
2018-03-12 7:48 ` Christoph Hellwig
2018-03-12 12:15 ` Mikulas Patocka
2018-03-12 12:15 ` Mikulas Patocka
2018-05-18 15:44 ` dm-writecache Mike Snitzer
2018-05-18 15:44 ` dm-writecache Mike Snitzer
2018-05-18 15:54 ` dm-writecache Dan Williams
2018-05-18 15:54 ` dm-writecache Dan Williams
2018-05-18 20:12 ` dm-writecache Mikulas Patocka
2018-05-18 20:12 ` dm-writecache Mikulas Patocka
2018-05-18 20:14 ` dm-writecache Dan Williams
2018-05-18 20:14 ` dm-writecache Dan Williams
2018-05-18 22:00 ` dm-writecache Mikulas Patocka
2018-05-18 22:00 ` dm-writecache Mikulas Patocka
2018-05-18 22:10 ` dm-writecache Dan Williams
2018-05-18 22:10 ` dm-writecache Dan Williams
2018-03-09 3:26 ` [dm-devel] [PATCH] dm-writecache Mikulas Patocka
2018-03-09 3:26 ` Mikulas Patocka
2018-03-12 7:50 ` Christoph Hellwig
2018-03-12 7:50 ` Christoph Hellwig
2018-03-12 12:12 ` Mikulas Patocka
2018-03-12 12:12 ` Mikulas Patocka
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=CAPcyv4gBUt5NYK2Lx0dMZAnENeSgKm3KaUvY9kkqB+PNPyQu4w@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mpatocka@redhat.com \
--cc=msnitzer@redhat.com \
/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.