All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@lst.de>,
	James Bottomley <jbottomley@parallels.com>,
	Sumit Saxena <sumit.saxena@avagotech.com>,
	Kashyap Desai <kashyap.desai@avagotech.com>,
	linux-scsi@vger.kernel.org, Webb Scales <webbnh@hp.com>,
	Don Brace <don.brace@pmcs.com>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] megaraid_sas: Enable shared host tag map
Date: Tue, 25 Nov 2014 17:30:14 +0100	[thread overview]
Message-ID: <20141125163014.GA2614@lst.de> (raw)
In-Reply-To: <5474968C.2080800@suse.de>

On Tue, Nov 25, 2014 at 03:47:40PM +0100, Hannes Reinecke wrote:
> I'd rather have a single map to get request/tags from; otherwise
> we'd be arbitrarily starving internal requests even though the
> 'main' tag map is empty.

At least in blk-mq the assumption is that a driver needs very few
internal tags, and it might need access to them in "emergency"
situations like resets or aborts.

> My plan was more to mark a certain range of tags as 'reserved',
> and add another helper/argument to allow to dip into the reserved
> pool, too.

We can add this as optional behavior, but I think the existing blk-mq
behavior is a good default.

> A tentative patch is attached.
> Idea is to call blk_queue_init_tags() with the actual tag size and
> then blk_resize_tags() to limit the number of tags for the request
> queue.
> The driver can then use 'blk_allocate_tag' with the appropriate max
> depth to get tags from the range [max_depth:real_max_depth].

I'd much prefer the blk-mq approach with two maps.  Either way please
make sure whatever you come up is compatible with blk-mq.

  reply	other threads:[~2014-11-25 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 15:33 [PATCH] megaraid_sas: Enable shared host tag map Hannes Reinecke
2014-11-24 15:35 ` Christoph Hellwig
2014-11-24 15:51   ` Hannes Reinecke
2014-11-24 15:59     ` Kashyap Desai
2014-11-25 14:31     ` Christoph Hellwig
2014-11-25 14:47       ` Hannes Reinecke
2014-11-25 16:30         ` Christoph Hellwig [this message]
2014-11-25 15:03       ` Kashyap Desai
2014-11-25 16:34         ` Christoph Hellwig
2014-11-24 15:52   ` Kashyap Desai

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=20141125163014.GA2614@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=don.brace@pmcs.com \
    --cc=hare@suse.de \
    --cc=jbottomley@parallels.com \
    --cc=kashyap.desai@avagotech.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sumit.saxena@avagotech.com \
    --cc=webbnh@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.