public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Johann Lombardi <johann.lombardi@bull.net>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [RFC] scsi: allow to increase the maximum number of sg entries
Date: Thu, 19 Apr 2007 08:30:36 +0200	[thread overview]
Message-ID: <20070419063036.GG13565@lombardij> (raw)
In-Reply-To: <1176895924.3671.100.camel@mulgrave.il.steeleye.com>

On Wed, Apr 18, 2007 at 07:32:03AM -0400, James Bottomley wrote:
> I don't think so: simply increasing the phys segments has no effect on a
> fully fragmented sg list if the hw segments doesn't go up to match it.

Yes, of course. It is then up to each scsi lld to increase max_hw_segments
accordingly. Increasing the phys segments seemed to me to be the first logical
step.
FYI, I tested the patch with lpfc and LPFC_SG_SEG_CNT set to 1024.

> Since changing the hw segments necessitates driver work, I'd really like
> to see justification in terms of throughput figures versus transfer size
> rather than vague assertions that bigger is better.

Sure. A full survey (done with sgp_dd) of DDN S2A9550 was posted on the
lustre-discuss mailing list in January:
https://mail.clusterfs.com/pipermail/lustre-discuss/2007-January/002795.html
http://mail.clusterfs.com/pipermail/lustre-discuss/attachments/20070118/8d6a4e79/9500-sgp_dd-0001.xls

For instance, here are the results obtained with 32 threads / 32 regions and
write-back caching disabled:

Transfer size     Throughput (Write)   Throughput (Read)  
512KB             36MB/s               108MB/s
1MB               60MB/s               108MB/s
2MB               96MB/s               165MB/s
4MB               144MB/s              228MB/s

Johann

      reply	other threads:[~2007-04-19  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-18  8:21 [RFC] scsi: allow to increase the maximum number of sg entries Johann Lombardi
2007-04-18 11:32 ` James Bottomley
2007-04-19  6:30   ` Johann Lombardi [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=20070419063036.GG13565@lombardij \
    --to=johann.lombardi@bull.net \
    --cc=James.Bottomley@SteelEye.com \
    --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