All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: mike.miller@hp.com
Cc: alpm@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 12:14:43 -0400	[thread overview]
Message-ID: <407428F3.90004@pobox.com> (raw)
In-Reply-To: <20040406201030.GB2554@beardog.cca.cpqcorp.net>

mikem@beardog.cca.cpqcorp.net wrote:
> This patch adds per logical device queues to the HP cciss driver. It currently only implements a single lock but when time permits I will provide that funtionality. Thanks to Jeff Garzik for providing some sample code.
> This patch built against 2.6.5. Please consider this for inclusion.


I appreciate the credit but I don't see that it addressed my original 
objection -- the starvation issue.

Do you cap the number of per-array requests a "1024 / n_arrays", or 
something like that?  You mentioned that the hardware has a maximum of 
1024 outstanding commands, for all devices.  The two typical solutions 
are a round-robin queue (see carmel.c) or limiting each array such that 
if all arrays are full of commands, the total outstanding never exceeds 
1024.

This patch may be OK for -mm, I would rather not see it go upstream -- 
it seems to me you are choosing to decrease stability to obtain a 
performance increase.  I think you can increase performance without 
decreasing stability.

	Jeff




  reply	other threads:[~2004-04-07 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06 20:10 cciss updates for 2.6.6xxx [1/2] mikem
2004-04-07 16:14 ` 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-07 19:11 Miller, Mike (OS Dev)
2004-04-07 19:42 ` 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=407428F3.90004@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alpm@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 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.