Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Jul 2011 15:04:38 -0700
From:      Kevin Oberman <kob6558@gmail.com>
To:        Scott Long <scottl@samsco.org>
Cc:        markmc@dataabstractsolutions.com, "freebsd-stable@freebsd.org Stable" <freebsd-stable@freebsd.org>, John Baldwin <jhb@freebsd.org>
Subject:   Re: disable 64-bit dma for one PCI slot only?
Message-ID:  <CAN6yY1sSuvHcRp1o4jSf61bhXYffreT12SWkoHgb6yPWn91=ng@mail.gmail.com>
In-Reply-To: <4F739848-E3CE-4E2C-A91E-90F33410E7AC@samsco.org>
References:  <4E20BA23.13717.66C6F57@markmcconnell.iinet.com> <201107181402.12755.jhb@freebsd.org> <797CACDE-729E-4F3A-AEFF-531C00C2B83A@samsco.org> <201107181714.07827.jhb@freebsd.org> <4F739848-E3CE-4E2C-A91E-90F33410E7AC@samsco.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 18, 2011 at 2:22 PM, Scott Long <scottl@samsco.org> wrote:
>
> On Jul 18, 2011, at 3:14 PM, John Baldwin wrote:
>
>> On Monday, July 18, 2011 5:06:40 pm Scott Long wrote:
>>> On Jul 18, 2011, at 12:02 PM, John Baldwin wrote:
>>>> On Friday, July 15, 2011 6:07:31 pm Mark McConnell wrote:
>>>>> Dear folks,
>>>>>
>>>>> I have two LSI raid cards, one of which (SCSI 320-I) supports
>>>>> 64-bit DMA when 4GB+ of DDR is present and another which
>>>>> does not (SATA 150-D) . =A0Consquently I've disabled 64-bit
>>>>> addressing for amr devices.
>>>>>
>>>>> I would like to disable 64-bit addressing for the SATA card, but
>>>>> permit it for the SCSI card. =A0Is this possible?
>>>>
>>>> You'd have to hack the driver perhaps to only disable 64-bit DMA for c=
ertain
>>>> PCI IDs. =A0It probably already does this?
>>>>
>>>
>>> The driver already had a table for determining 64bit DMA based on the P=
CI ID.
>>> I guess there's a mistake in the table for this particular card. =A0I t=
hink that
>>> changing the following line to remove the AMR_ID_DO_SG64 flag will fix =
the
>>> problem:
>>>
>>> =A0 =A0{0x1000, 0x1960, AMR_ID_QUARTZ | AMR_ID_DO_SG64 | AMR_ID_PROBE_S=
IG},
>>>
>>> Actually, what's probably going on is that the driver is only looking a=
t the
>>> vendor and device id's, and is ignoring the subvendor and subdevice id'=
s that
>>> would give it a better clue on the exact hardware in use. =A0Fixing the=
 driver
>>> to look at all 64bits of id info (and take into account wildcards where
>>> needed) would be a good project, if anyone is interested.
>>>
>>> Btw, I *HATE* the "chip" and "card" identifiers used in pciconf. =A0Can=
 we
>>> change it to emit the standard (sub)vendor/(sub)device terminology?
>>
>> Oh, yeah. =A0I hate that too. =A0Would you want them as 4 separate entit=
ies or to
>> just rename the labels to 'devid' and 'subdevid'?
>>
>
> If we're going to change it, might as well break it down into 4 fields. =
=A0Maybe we retain the
> old format under a legacy switch and/or env variable for users that have =
tools that parse
> the output (cough yahoo cough).

Pretty please! This would be wonderful.
--=20
R. Kevin Oberman, Network Engineer - Retired
E-mail: kob6558@gmail.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1sSuvHcRp1o4jSf61bhXYffreT12SWkoHgb6yPWn91=ng>