linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Reducing I/O latency
Date: Thu, 17 May 2012 16:39:39 +0000	[thread overview]
Message-ID: <4FB529CB.7050507@acm.org> (raw)

Hello,

Recently I have been looking for opportunities to reduce command
processing latency in the Linux SCSI initiator stack. I've noticed the
following:
- In drivers/scsi/scsi.c memory for the SCSI command and the SCSI sense
  data are allocated separately. Would it be a good idea to combine
  scsi_host_cmd_pool.cmd_slab and scsi_host_cmd_pool.sense_slab into a
  single kmem_cache or would this break something ?
- While running an I/O workload that was using eight LUNs (two hosts
  with four LUNs each) I noticed huge lock contention on the spinlock in
  scsi_host_cmd_pool.cmd_slab. Has anyone already tried to modify the
  code in drivers/scsi/scsi.c such that there is one pool per LUN
  instead of one pool for all LUNs of all hosts ? Note: the
  scsi_sg_pools array in drivers/scsi/scsi_lib.c is also shared over
  all LUNs.

Thanks,

Bart.

                 reply	other threads:[~2012-05-17 16:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4FB529CB.7050507@acm.org \
    --to=bvanassche@acm.org \
    --cc=linux-scsi@vger.kernel.org \
    /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).