All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Laurence Oberman <loberman@redhat.com>
Cc: dgilbert@interlog.com,
	Linux SCSI List <linux-scsi@vger.kernel.org>,
	Ewan Milne <emilne@redhat.com>
Subject: Re: sg driver, sg_io and sg tablesize
Date: Thu, 2 Mar 2017 19:41:39 +0800	[thread overview]
Message-ID: <20170302114139.GA22977@lemon.lan> (raw)
In-Reply-To: <50601133.40845997.1488406291147.JavaMail.zimbra@redhat.com>

On Wed, 03/01 17:11, Laurence Oberman wrote:
> This was suggested by Ewan and is the best way to know what the actual max I/O
> size for sg_io would be for the LPFC driver.

This sounds silly, why is there a "lame" max I/O size as in max_sectors_kb,
that is unusable because of a more limiting max_segments, and an "actual max
I/O size" as derived from the latter? What is the reason of the contradiction
here?

Fam

      reply	other threads:[~2017-03-02 11:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <178924924.40657267.1488382475137.JavaMail.zimbra@redhat.com>
2017-03-01 15:44 ` sg driver, sg_io and sg tablesize Laurence Oberman
2017-03-01 22:11   ` Laurence Oberman
2017-03-02 11:41     ` Fam Zheng [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=20170302114139.GA22977@lemon.lan \
    --to=famz@redhat.com \
    --cc=dgilbert@interlog.com \
    --cc=emilne@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=loberman@redhat.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.