From: Kashyap Desai <kashyap.desai@avagotech.com>
To: Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <jbottomley@parallels.com>,
Sumit Saxena <sumit.saxena@avagotech.com>,
linux-scsi@vger.kernel.org
Subject: RE: [PATCH] megaraid_sas: Enable shared host tag map
Date: Mon, 24 Nov 2014 21:22:49 +0530 [thread overview]
Message-ID: <cec16f1d245f8e7b2dbe5ccbd7455cc3@mail.gmail.com> (raw)
In-Reply-To: <20141124153558.GA27364@lst.de>
> -----Original Message-----
> From: Christoph Hellwig [mailto:hch@lst.de]
> Sent: Monday, November 24, 2014 9:06 PM
> To: Hannes Reinecke
> Cc: James Bottomley; Sumit Saxena; Kashyap Desai; Christoph Hellwig;
linux-
> scsi@vger.kernel.org
> Subject: Re: [PATCH] megaraid_sas: Enable shared host tag map
>
> On Mon, Nov 24, 2014 at 04:33:55PM +0100, Hannes Reinecke wrote:
> > The megaraid SAS driver uses a shared host tag map internally, so we
> > should be telling the block layer about it.
>
> But it doesn't make use of request->tag yet. This would only be useful
if you
> got rid of the internal tag allocator.
I have patch for code changes in this particular area and that is
currently under internal test cycle.
Next patch series will start using shared blk tag for internal MPT frame
allocation. It will get-rid-off MPT frame pool link list completely and
also does lots of refactor w.r.t MFI/MPT frame corruption issue. Using
shared blk tag gave good performance improvement as driver completely
removed mpt frame spin lock used in megasas_get_cmd_fusion/
megasas_return_cmd_fusion.
~ Kashyap
prev parent reply other threads:[~2014-11-24 15:52 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
2014-11-25 15:03 ` Kashyap Desai
2014-11-25 16:34 ` Christoph Hellwig
2014-11-24 15:52 ` Kashyap Desai [this message]
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=cec16f1d245f8e7b2dbe5ccbd7455cc3@mail.gmail.com \
--to=kashyap.desai@avagotech.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sumit.saxena@avagotech.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.