From: Dave C Boutcher <sleddog@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [patch] ibmvscsi.c: remove max-sectors module parm
Date: Thu, 23 Dec 2004 18:36:20 -0600 [thread overview]
Message-ID: <20041224003620.GA31981@cs.umn.edu> (raw)
In-Reply-To: <1103835435.5290.45.camel@mulgrave>
On Thu, Dec 23, 2004 at 02:57:15PM -0600, James Bottomley wrote:
> On Thu, 2004-12-23 at 14:01 -0600, Dave C Boutcher wrote:
> > The patches I submitted on Tuesday are incremental on top of the four
> > patches from November 29th. Let me know if you would like the
> > November 29th patches re-sent.
>
> Actually, just the limit size of I/O requests with the two patches
> rolled together (or is there nothing left of this now?)
I'm not sure I parse that...but in any case, one of the four patches
from November limited the size of the I/O requests based on information
from the SCSI target, with a default value in case the target doesn't
tell us. I got overly clever and made the default value a module
parameter. Jens pointed out that I was being redundant, since
there are other ways to set max sectors. The patch I submitted
on Tuesday leaves the basic function intact (setting max I/O size
based on input from the target) and just removes the redundant module
parameter.
--
Dave Boutcher
next prev parent reply other threads:[~2004-12-24 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 22:36 [patch] ibmvscsi.c: remove max-sectors module parm Dave C Boutcher
2004-12-23 19:03 ` James Bottomley
2004-12-23 20:01 ` Dave C Boutcher
2004-12-23 20:57 ` James Bottomley
2004-12-24 0:36 ` Dave C Boutcher [this message]
2004-12-31 0:04 ` James Bottomley
2004-12-31 17:32 ` Dave C Boutcher
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=20041224003620.GA31981@cs.umn.edu \
--to=sleddog@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=boutcher@cs.umn.edu \
--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 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.