Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030791Ab3HITLn (ORCPT ); Fri, 9 Aug 2013 15:11:43 -0400 Received: from g6t0184.atlanta.hp.com ([15.193.32.61]:28636 "EHLO g6t0184.atlanta.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030485Ab3HITLl (ORCPT ); Fri, 9 Aug 2013 15:11:41 -0400 Date: Fri, 9 Aug 2013 14:11:40 -0500 From: scameron@beardog.cce.hp.com To: linux-kernel@vger.kernel.org Cc: axboe@kernel.dk, tj@kernel.org, scameron@beardog.cce.hp.com Subject: Re: Question about REQ_FLUSH and bios with data Message-ID: <20130809191140.GM9905@beardog.cce.hp.com> References: <20130809190934.GL9905@beardog.cce.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130809190934.GL9905@beardog.cce.hp.com> User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1242 Lines: 36 On Fri, Aug 09, 2013 at 02:09:34PM -0500, scameron@beardog.cce.hp.com wrote: > > So, I'm working on a block driver using the make_request_fn > interface, and have to handle a bio that comes in with > (bi_rw & REQ_FLUSH) set AND data to transfer. > > According to Documentation/block/writeback_cache_control.txt: > > The REQ_FLUSH flag can be OR ed into the r/w flags of a > bio submitted from the filesystem and will make sure the > volatile cache of the storage device has been flushed > before the actual I/O operation is started. > > So I've written code that handles that case, along with the > various error cases I might encounter, I think, which leads > to my question: > > How do I get such a bio with a data transfer AND the REQ_FLUSH bit > set to come into the driver? Just wondering how to test this case. > > Thanks, > > (I cc'ed Tejun Heo just because his name is in block/blk-flush.c) > > -- steve Oops, you'd think I'd know Jens's email address by now. -- steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/