[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x49611qaeqk.fsf@segfault.boston.devel.redhat.com>
Date: Wed, 28 Oct 2015 17:02:27 -0400
From: Jeff Moyer <jmoyer@...hat.com>
To: "Williams\, Dan J" <dan.j.williams@...el.com>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nvdimm\@ml01.01.org" <linux-nvdimm@...1.01.org>,
"hch\@lst.de" <hch@....de>,
"akpm\@linux-foundation.org" <akpm@...ux-foundation.org>,
"axboe\@fb.com" <axboe@...com>, "jack\@suse.com" <jack@...e.com>,
"david\@fromorbit.com" <david@...morbit.com>,
"jack\@suse.cz" <jack@...e.cz>
Subject: Re: [PATCH v2 2/5] dax: increase granularity of dax_clear_blocks() operations
"Williams, Dan J" <dan.j.williams@...el.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@...hat.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists