From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Jens Axboe'" <axboe@suse.de>,
"Ananiev, Leonid I" <leonid.i.ananiev@intel.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/1] indirect function calls elimination in IO scheduler
Date: Mon, 17 Oct 2005 12:25:01 -0700 [thread overview]
Message-ID: <200510171925.j9HJPKg12681@unix-os.sc.intel.com> (raw)
In-Reply-To: <20051017175858.GY2811@suse.de>
Jens Axboe wrote on Monday, October 17, 2005 10:59 AM
> you cannot ref count a statically embedded structure. It has to be
> dynamically allocated.
I'm confused. For every block device queue, there is one unique
elevator_t structure allocated via kmalloc. And vice versa, one
elevator_t has only one request_queue points to it. This elevator_t
structure is per q since it has pointer to per-queue elevator
private data.
Since it is always one to one relationship, ref count is predictable
and static. I see there are ref count on q->elevator, But it is
always 2: one from object instantiation and one from adding an sysfs
hierarchy directory. In this case, I don't see the difference.
Am I missing something?
- Ken
next prev parent reply other threads:[~2005-10-17 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 17:01 Ananiev, Leonid I
2005-10-17 17:58 ` [PATCH " Jens Axboe
2005-10-17 19:25 ` Chen, Kenneth W [this message]
2005-10-17 19:40 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2005-12-01 17:18 Ananiev, Leonid I
2005-10-20 5:11 Ananiev, Leonid I
2005-10-19 13:08 Ananiev, Leonid I
2005-10-19 13:56 ` Arjan van de Ven
2005-10-18 13:15 Ananiev, Leonid I
2005-10-17 16:12 Ananiev, Leonid I
2005-10-18 2:44 ` Randy.Dunlap
2005-10-16 22:28 Ananiev, Leonid I
2005-10-17 3:41 ` [PATCH " Randy.Dunlap
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=200510171925.j9HJPKg12681@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=axboe@suse.de \
--cc=leonid.i.ananiev@intel.com \
--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
all inboxes | Powered by JetHome®