From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [PATCH 1/2] block: introduce BIO_IN_FLIGHT flag Date: Mon, 9 Jan 2012 08:41:48 -0800 Message-ID: <20120109164148.GB21732@google.com> References: <1324996113-1837-1-git-send-email-namhyung@gmail.com> <1324996113-1837-2-git-send-email-namhyung@gmail.com> <20120109015628.GB16360@mtj.dyndns.org> <4F0A57A7.4070508@lge.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jens Axboe , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Namhyung Kim Return-path: Content-Disposition: inline In-Reply-To: <4F0A57A7.4070508@lge.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hello, On Mon, Jan 09, 2012 at 11:57:43AM +0900, Namhyung Kim wrote: > I understand your concerns. However, the blktrace cannot get > bio->bi_flags info in its current form AFAIK. Doing it will require > extending struct blk_io_trace and it'll cause a compatibility issue, > I guess. Umm? Why can't blk_add_trace_bio_complete() look at the flags (or whatever other states) to decide to fire off BLK_TA_COMPLETE or not? What's the difference? No userland visible change is necessary at all. Just make blktrace.c do the right thing. Am I missing something? Thanks. -- tejun