From: Jeff Moyer <jmoyer@redhat.com>
To: "Williams\, Dan J" <dan.j.williams@intel.com>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm\@ml01.01.org" <linux-nvdimm@ml01.01.org>,
"hch\@lst.de" <hch@lst.de>,
"akpm\@linux-foundation.org" <akpm@linux-foundation.org>,
"axboe\@fb.com" <axboe@fb.com>, "jack\@suse.com" <jack@suse.com>,
"david\@fromorbit.com" <david@fromorbit.com>,
"jack\@suse.cz" <jack@suse.cz>
Subject: Re: [PATCH v2 2/5] dax: increase granularity of dax_clear_blocks() operations
Date: Wed, 28 Oct 2015 17:02:27 -0400 [thread overview]
Message-ID: <x49611qaeqk.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <1445554654.17208.14.camel@intel.com> (Dan J. Williams's message of "Thu, 22 Oct 2015 22:57:37 +0000")
"Williams, Dan J" <dan.j.williams@intel.com> writes:
> The problem is that intervening call to cond_resched(). I later want to
> inject an rcu_read_lock()/unlock() pair to allow flushing active
> dax_map_atomic() usages at driver teardown time [1]. But, I think the
> patch stands alone as a cleanup outside of that admittedly hidden
> motivation.
I'm not going to split hairs.
Reviewed-by: Jeff Moyer <jmoyer@redhat.com>
next prev parent reply other threads:[~2015-10-28 21:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 17:10 [PATCH v2 0/5] block, dax: updates for 4.4 Dan Williams
2015-10-22 17:10 ` [PATCH v2 1/5] pmem, dax: clean up clear_pmem() Dan Williams
2015-10-22 20:48 ` Jeff Moyer
2015-10-22 22:29 ` Dan Williams
2015-10-28 21:01 ` Jeff Moyer
2015-10-27 17:31 ` Ross Zwisler
2015-10-22 17:10 ` [PATCH v2 2/5] dax: increase granularity of dax_clear_blocks() operations Dan Williams
2015-10-22 21:04 ` Jeff Moyer
2015-10-22 22:57 ` Williams, Dan J
2015-10-28 21:02 ` Jeff Moyer [this message]
2015-10-22 17:10 ` [PATCH v2 3/5] block, dax: fix lifetime of in-kernel dax mappings with dax_map_atomic() Dan Williams
2015-10-28 20:15 ` Jeff Moyer
2015-10-22 17:10 ` [PATCH v2 4/5] block: introduce bdev_file_inode() Dan Williams
2015-10-22 20:37 ` Jan Kara
2015-10-28 20:16 ` Jeff Moyer
2015-10-22 17:10 ` [PATCH v2 5/5] block: enable dax for raw block devices Dan Williams
2015-10-28 20:50 ` Jeff Moyer
2015-10-29 7:14 ` 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=x49611qaeqk.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®