From: Christoph Hellwig Subject: Re: [PATCH 2/2][v2] blk-plug: don't flush nested plug lists Date: Wed, 8 Apr 2015 18:13:55 +0200 Message-ID: <20150408161355.GA16052@lst.de> References: <1428347694-17704-1-git-send-email-jmoyer@redhat.com> <1428347694-17704-2-git-send-email-jmoyer@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jens Axboe , Ming Lei , Konrad Rzeszutek Wilk , Roger Pau Monn?? , Alasdair Kergon , Mike Snitzer , Neil Brown , "Nicholas A. Bellinger" , Alexander Viro , Chris Mason , Josef Bacik , David Sterba , Theodore Ts'o , Andreas Dilger , Jaegeuk Kim , Changman Lee , Steven Whitehouse , Mikulas Patocka , Andrew Morton , Rik van Riel , Johannes Weiner , Mel Gorman , Trond Myklebust , Anna Schumaker Return-path: Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-Id: linux-ext4.vger.kernel.org This looks good, but without the blk_finish_plug argument we're bound to grow programming mistakes where people forget it. Any chance we could have annotations similar to say rcu_read_lock/rcu_read_unlock or the spinlocks so that sparse warns about it? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org