From: Christoph Hellwig <hch@infradead.org>
To: scameron@beardog.cce.hp.com
Cc: linux-scsi@vger.kernel.org, jbottomley@parallels.com,
martin.petersen@oracle.com, thenzl@redhat.com, hare@suse.de,
hch@infradead.org, bvanassche@acm.org, axboe@kernel.dk,
elliott@hp.com, scott.teel@hp.com, webbnh@hp.com,
joseph.t.handzik@hp.com, justin.lindley@hp.com
Subject: Re: [RFC] hpsa: work in progress "lockless monster" patches
Date: Sat, 26 Jul 2014 08:32:32 -0700 [thread overview]
Message-ID: <20140726153232.GE1854@infradead.org> (raw)
In-Reply-To: <20140725192859.GU14599@beardog.cce.hp.com>
> Christoph Hellwig (1):
> reserve block tags in scsi host
So you found this one useful. This begs the question how we should
move forward with it, as it will only work with the blk-mq path in
it's current form.
I can see three ways:
- we implement equivalent functionality in the old block tagging code
and make it available for any driver
- we require drivers specific workarounds for the !mq path
- we allow drivers to force the use of the blk-mq path if they want
to use advanced features like this. This might become nessecary
anyway when we expose actual multiqueue support to LLDDs.
next prev parent reply other threads:[~2014-07-26 15:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 19:28 [RFC] hpsa: work in progress "lockless monster" patches scameron
2014-07-26 15:32 ` Christoph Hellwig [this message]
2014-07-27 15:24 ` Hannes Reinecke
2014-07-31 16:35 ` scameron
2014-07-30 14:55 ` Tomas Henzl
2014-07-30 20:33 ` Webb Scales
2014-07-31 13:56 ` Tomas Henzl
2014-07-31 15:16 ` scameron
2014-08-04 13:13 ` Tomas Henzl
2014-08-01 16:40 ` Webb Scales
2014-08-04 13:36 ` Tomas Henzl
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=20140726153232.GE1854@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=elliott@hp.com \
--cc=hare@suse.de \
--cc=jbottomley@parallels.com \
--cc=joseph.t.handzik@hp.com \
--cc=justin.lindley@hp.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=scameron@beardog.cce.hp.com \
--cc=scott.teel@hp.com \
--cc=thenzl@redhat.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 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).