From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: axboe@suse.de
Subject: Re: [PATCH] Proper block queue reference counting
Date: Thu, 07 Aug 2003 10:36:44 -0400 [thread overview]
Message-ID: <3F3263FC.5030100@pobox.com> (raw)
In-Reply-To: <200308070909.h7799QHg022029@hera.kernel.org>
I like the patch, but see two problems:
1) You convert drivers to dynamically allocated queues... who is freeing
the queues? unregister_blkdev? It's a bit non-obvious to say the
least, since you patches (for example, the first one, to stram.c)
obviously switch blk_init_queue to dynamically allocate a queue... but
you do not add code to remove the final reference in modprobe. The
standard driver-facing API dictates that the driver calls foo_put
itself, in the driver, rather than have it done implicitly.
2) the blk_init_queue really should change names, IMO. The other
subsystems in the kernel tend to use a "foo_alloc" or "alloc_foo"
pattern when creating new objects. blk_alloc_queue, or simply blk_alloc?
Jeff
next parent reply other threads:[~2003-08-07 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200308070909.h7799QHg022029@hera.kernel.org>
2003-08-07 14:36 ` Jeff Garzik [this message]
2003-08-07 14:50 ` [PATCH] Proper block queue reference counting Jens Axboe
2003-08-07 14:56 ` Jeff Garzik
2003-08-07 15:00 ` 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=3F3263FC.5030100@pobox.com \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox