From: Jeff Garzik <jgarzik@pobox.com>
To: "Miller, Mike (OS Dev)" <mike.miller@hp.com>
Cc: akpm@odsl.org, axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: cciss updates for 2.6.6xxx [1/2]
Date: Wed, 07 Apr 2004 15:42:26 -0400 [thread overview]
Message-ID: <407459A2.4030009@pobox.com> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF105BC2012@cceexc23.americas.cpqcorp.net>
Miller, Mike (OS Dev) wrote:
> I like the idea of capping max commands based on the number of arrays. One problem is that we can add or remove a logical drive during runtime. How would Linux handle us reshuffling the max commands for each queue?
What is the maximum number of logical drives?
If you always assume the maximum number of logical drives are configured
(let's say 32), then you can calculate based on that:
1024 / 32 logical drives == 32 commands per logical drive
It certainly gets a bit more complex, if you truly want to handle
something other than "hardcode max # of logical drives"... I would
suggest going to a round-robin anti-starvation approach at that point,
like what I do in carmel.c. The Carmel hardware has a single hardware
queue for all of its 8 SATA ports, which is similar to cciss having 1024
commands for all of its logical drives (if I understand things correctly).
Jeff
next prev parent reply other threads:[~2004-04-07 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 19:11 cciss updates for 2.6.6xxx [1/2] Miller, Mike (OS Dev)
2004-04-07 19:42 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-07 16:21 Miller, Mike (OS Dev)
2004-04-07 16:33 ` Jeff Garzik
2004-04-06 20:10 mikem
2004-04-07 16:14 ` Jeff Garzik
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=407459A2.4030009@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@odsl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.miller@hp.com \
/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;
as well as URLs for NNTP newsgroup(s).