Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: va stg2010 <va.storage2010@gmail.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: scsi LLD implementation question
Date: Fri, 25 Feb 2011 14:34:40 -0500	[thread overview]
Message-ID: <1298662480.2459.63.camel@mulgrave.site> (raw)
In-Reply-To: <AANLkTikZqXCzJcRL3cL16w1O+MoDecy4N9XK14yzKd3D@mail.gmail.com>

On Fri, 2011-02-25 at 11:19 -0800, va stg2010 wrote:
> Thanks !
> There is a 32-bit tag  to refer back  the queue(for pending commands)
> when responses are posted back by HBA.   Suppose the HBA is  receiving
> commands from multiple initiators because the host has virtualized
> initiator environment, now in this case  one single large queue is
> good enough or there should be pending-commands-queue per virtual
> initiator or pending-command-queue per disks.

It doesn't have to be virtualised; this is the normal situation on a
SAN.  For a pending queue, the question is merely how to do efficient
lookup.  Some drivers use a fixed offset list (with the offset in the
completion tag) ... I suppose a radix tree would be a good way to go for
particularly large pending queues.

> Just want to minimize the  locking contentions  and  maximize
> parallelism in  SCSI  I/O to multiple disks from multiple virtual
> initiators via my HBA.

To be honest, fixes offset lists are best then ... they can operated
locklessly.

James



      parent reply	other threads:[~2011-02-25 19:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=+6z4qRS7MGSNTyomtyQTu5A20iBF-T92xAPMA@mail.gmail.com>
2011-02-25 13:37 ` scsi LLD implementation question James Bottomley
2011-02-25 17:12   ` Bart Van Assche
2011-02-25 17:20     ` James Bottomley
2011-02-26  9:16       ` Bart Van Assche
     [not found]   ` <AANLkTikZqXCzJcRL3cL16w1O+MoDecy4N9XK14yzKd3D@mail.gmail.com>
2011-02-25 19:34     ` James Bottomley [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=1298662480.2459.63.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=va.storage2010@gmail.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