Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tbogendoerfer@suse.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Magnus Lindholm <linmag7@gmail.com>,
	linux-scsi@vger.kernel.org,
	James.Bottomley@hansenpartnership.com,
	martin.petersen@oracle.com
Subject: Re: [PATCH v3] scsi: qla1280.c
Date: Tue, 5 Nov 2024 09:33:21 +0100	[thread overview]
Message-ID: <20241105093321.3ad1c1a7@samweis> (raw)
In-Reply-To: <alpine.DEB.2.21.2411042134240.9262@angie.orcam.me.uk>

On Mon, 4 Nov 2024 21:52:36 +0000 (GMT)
"Maciej W. Rozycki" <macro@orcam.me.uk> wrote:

> On Mon, 4 Nov 2024, Magnus Lindholm wrote:
> 
> >  Use dma_get_required_mask() to determine an acceptable DMA_BIT_MASK 
> >  since on some platforms, qla1040 cards do not work with a 64-bit
> >  mask. For example, on alpha systems with more than 2GB ram a 64-bit DMA mask
> >  will result in filesystem corruption, but a 64-bit mask is required on
> >  IP30/MIPS.  
> 
>  This is missing the point, you get filesystem corruption because *your 
> card* does not support 64-bit DMA addressing and not because your Alpha 
> system has an issue with it.

I've checked one of my Octane boards and there are ISP1040B chips on
the board, so even ISP1040B is able to address 64bits.

How does the memory map look for more and 2GB ram on the ES40 ?

Thomas.

-- 
SUSE Software Solutions Germany GmbH
HRB 36809 (AG Nürnberg)
Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich

  reply	other threads:[~2024-11-05  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04 20:46 [PATCH v3] scsi: qla1280.c Magnus Lindholm
2024-11-04 21:52 ` Maciej W. Rozycki
2024-11-05  8:33   ` Thomas Bogendoerfer [this message]
2024-11-06 12:48     ` Maciej W. Rozycki
2024-11-05  1:49 ` Martin K. Petersen

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=20241105093321.3ad1c1a7@samweis \
    --to=tbogendoerfer@suse.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=linmag7@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox