From: Jens Axboe <axboe@suse.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ifdef blktrace debugging fields
Date: Tue, 1 Aug 2006 22:12:57 +0200 [thread overview]
Message-ID: <20060801201256.GE20108@suse.de> (raw)
In-Reply-To: <20060801134703.GG7006@martell.zuzino.mipt.ru>
On Tue, Aug 01 2006, Alexey Dobriyan wrote:
> On Tue, Aug 01, 2006 at 09:44:36AM +0200, Jens Axboe wrote:
> > Certainly. If Alexey adds the blkdev.h bit as well, we can go ahead with
> > it.
>
> Done. Originally I looked at slab size of task_struct and still
> recovering.
;-)
> [PATCH] ifdef blktrace debugging fields
>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> ---
>
> block/ll_rw_blk.c | 4 ++--
> include/linux/blkdev.h | 4 ++--
> include/linux/sched.h | 3 ++-
> kernel/fork.c | 2 ++
> 4 files changed, 8 insertions(+), 5 deletions(-)
>
> --- a/block/ll_rw_blk.c
> +++ b/block/ll_rw_blk.c
> @@ -1779,10 +1779,10 @@ static void blk_release_queue(struct kob
>
> if (q->queue_tags)
> __blk_queue_free_tags(q);
> -
> +#ifdef CONFIG_BLK_DEV_IO_TRACE
> if (q->blk_trace)
> blk_trace_shutdown(q);
> -
> +#endif
> kmem_cache_free(requestq_cachep, q);
> }
That can be made ifdef less, if you unconditionally call
blk_trace_shutdown() and just make that one do:
if (q->blk_trace) {
...
}
since that'll then do the right always. Please make that change, then
I'm fine with the patch.
--
Jens Axboe
next prev parent reply other threads:[~2006-08-01 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200608010657.k716vBWF004420@shell0.pdx.osdl.net>
[not found] ` <20060801071658.GG31908@suse.de>
[not found] ` <20060801002904.53407219.akpm@osdl.org>
[not found] ` <20060801074436.GJ31908@suse.de>
2006-08-01 13:47 ` [PATCH] ifdef blktrace debugging fields Alexey Dobriyan
2006-08-01 20:12 ` Jens Axboe [this message]
2006-08-01 22:49 ` [PATCH v3] " Alexey Dobriyan
2006-08-02 5:18 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060801201256.GE20108@suse.de \
--to=axboe@suse.de \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.