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: Tue, 10 Jan 2012 08:26:25 -0800 Message-ID: <20120110162625.GB20446@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> <20120109164148.GB21732@google.com> <4F0BC770.1090702@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, namhyung@gmail.com To: Namhyung Kim Return-path: Content-Disposition: inline In-Reply-To: <4F0BC770.1090702@lge.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hello, On Tue, Jan 10, 2012 at 02:06:56PM +0900, Namhyung Kim wrote: > Oh I misunderstood what you said. I was thinking about filtering in > pure userspace, but you meant in-kernel probe side. Yeah yeah. > Right, we can change the probe to filter BIO_BOUNCED case out. But > IMHO BIO_CLONED is different, since it usually routed to another > device as a separate IO request. I'll cook a patch for the former > soon. It'll probably get dup'd completions from rq and bio completions for request based drivers, right? Maybe there are better ways but blktrace may as well just ignore bio completions if request completions are happening. Thanks. -- tejun