From owner-freebsd-stable@FreeBSD.ORG Mon Jul 18 22:04:39 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 982B4106564A; Mon, 18 Jul 2011 22:04:39 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 44F928FC14; Mon, 18 Jul 2011 22:04:38 +0000 (UTC) Received: by gwb15 with SMTP id 15so1857745gwb.13 for ; Mon, 18 Jul 2011 15:04:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=n6W9sNJ107v+uPA5r2nJxrb1wG7eVgyA4oWAgNoSxEY=; b=SEEPrCHgc3Jw6CMPHPAzRpmbcKmTVmjbxJtTX+Dyi/3LRixD54mm9ku+izM3AkdTyY D9EtHPliLuve6PQ1z0/RmAvxvwbIUxnYNSvL8xthzJsxu7ig1MKL4pTcGhb+hCLKqCpC qDFhwd4tlqh1Y7AmvSLOR8woQdKbuHpanHvl0= MIME-Version: 1.0 Received: by 10.151.109.8 with SMTP id l8mr6524146ybm.27.1311026678429; Mon, 18 Jul 2011 15:04:38 -0700 (PDT) Received: by 10.151.27.21 with HTTP; Mon, 18 Jul 2011 15:04:38 -0700 (PDT) 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> Date: Mon, 18 Jul 2011 15:04:38 -0700 Message-ID: From: Kevin Oberman To: Scott Long Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: markmc@dataabstractsolutions.com, "freebsd-stable@freebsd.org Stable" , John Baldwin Subject: Re: disable 64-bit dma for one PCI slot only? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2011 22:04:39 -0000 On Mon, Jul 18, 2011 at 2:22 PM, Scott Long 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