Each driver instance is allocating some miscellaneous buffers + 1k * 9000s
bytes buffers. The 4th instance boot up issue seems only happen on m3000
Sparc server(8G memory). I guess m3000 dma region is somewhat limited. I am
wondering how I can know its dma region range.
Tom
--------------------------------------------------
From: "Garrett D'Amore" <[email protected]>
Sent: Saturday, July 24, 2010 3:35 PM
To: "Tom Chen" <[email protected]>
Cc: <[email protected]>
Subject: Re: [driver-discuss] dma memory allocation failure
How much are you allocating? DMA regions may indeed be limited...
- Garrett
On Sat, 2010-07-24 at 13:44 -0700, Tom Chen wrote:
a-able memory per server is limited, no matter what the total system
memory is? how do I know the limitation? Or, is this related to the
dma attribute I am using?
ddi_dma_attr_t dma_attr_rbuf = {
DMA_ATTR_V0, /* dma_attr_version */
0, /* low DMA address range */
(uint64_t)0x
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
