Re: [PATCH] hpsa: SCSI driver for HP Smart Array controllers

[James Bottomley]

On Fri, 2009-03-06 at 15:18 -0600, scameron@xxxxxxxxxxxxxxxxxxxxxxx
wrote:
> On Fri, Mar 06, 2009 at 12:59:48PM -0800, Grant Grundler wrote:
> > On Fri, Mar 6, 2009 at 6:38 AM,  <scameron@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > ...
> > > The command buffers have to be in the first 4GB of memory, as the command
> > > register is only 32 bits, so they are allocated by pci_alloc_consistent.
> > 
> > Huh?!!
> > ISTR the mpt2sas driver is indicating it can handle 64-bit DMA masks for
> > both streaming and control data. I need to double check to be sure of that.
> 
> it is something specific to smart array.  The command register that we
> stuff the bus address of the command into is only 32 bits wide.  Everything
> else it does is 64 bits.
> > 
> > 
> > > However, the chained SG lists don't have that limitation, so I think they
> > > can be kmalloc'ed, and so not chew up and unreasonable amount of the
> > > pci_alloc_consistent memory and get a larger number of SGs.   ...right?
> > > Maybe that's the better way to do it.
> > 
> > I thought the driver was tracking this and using the appropriate construct
> > based on which DMA mask is in effect.
> 
> The DMA mask is insufficiently expressive to describe the limitations and
> capabilities of the Smart array.  There's no way to describe with a single
> DMA mask that the command register is 32-bits, but everything else is 64
> bits.

Actually, there is ... it's what you're doing: use a coherent mask of 32
bits and a dma mask of 64bits.

The aic79xx has exactly the same problem (its internal sequencer only
has a 32 bit wide programme counter, so it can only execute sequencer
scripts if they're in the first 4GB of memory).  I think it's fairly
common amongst intelligent controllers that are old enough to have been
32 bit only but which got extended to work on 64 bits.

To get ordinary memory for this, you just use GFP_DMA32 as has been
previously stated.

James


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/