linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Tomasz Torcz <tomek@pipebreaker.pl>, linux-scsi@vger.kernel.org
Subject: Re: can't access LUN >2TB with aic7xxx, Infortrend EonStor and 2.6.31-rc1
Date: Mon, 29 Jun 2009 08:56:29 -0600	[thread overview]
Message-ID: <20090629145629.GP5480@parisc-linux.org> (raw)
In-Reply-To: <1246285984.3838.9.camel@mulgrave.site>

On Mon, Jun 29, 2009 at 09:33:03AM -0500, James Bottomley wrote:
> +++ b/drivers/scsi/aic7xxx/aic79xx_osm.c
> @@ -1241,6 +1241,7 @@ ahd_linux_register_host(struct ahd_softc *ahd, struct scsi_host_template *templa
>  	host->max_lun = AHD_NUM_LUNS;
>  	host->max_channel = 0;
>  	host->sg_tablesize = AHD_NSEG;
> +	host->max_cmd_len = 32;

James and I are discussing this off-list, but 32 is clearly not correct
for aic79xx as the tag number will overwrite the command (or possibly
vice versa).  We're just picking over the various options at the moment.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

      reply	other threads:[~2009-06-29 14:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 13:08 can't access LUN >2TB with aic7xxx, Infortrend EonStor and 2.6.31-rc1 Tomasz Torcz
2009-06-29 13:34 ` Matthew Wilcox
2009-06-29 13:40   ` Drew
2009-06-29 13:47     ` Matthew Wilcox
2009-06-29 14:54       ` Drew
2009-06-29 13:46   ` Matthew Wilcox
2009-06-29 16:13     ` Tomasz Torcz
2009-06-30  9:40     ` Tomasz Torcz
2009-06-30 14:45       ` James Bottomley
2009-06-30 15:48       ` James Bottomley
2009-07-01  6:10         ` Tomasz Torcz
2009-07-01 14:19           ` James Bottomley
2009-06-29 14:33 ` James Bottomley
2009-06-29 14:56   ` Matthew Wilcox [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=20090629145629.GP5480@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tomek@pipebreaker.pl \
    /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).