[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1334336563.2606.3.camel@bwh-desktop.uk.solarflarecom.com>
Date: Fri, 13 Apr 2012 18:02:43 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: xiong <xiong@....qualcomm.com>
CC: <davem@...emloft.net>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <qca-linux-team@...lcomm.com>,
<nic-devel@...lcomm.com>, linux-pci <linux-pci@...r.kernel.org>
Subject: Re: [PATCH 12/37] atl1c: restore max-read-request-size in Device
Conrol Register
On Fri, 2012-04-13 at 08:14 +0800, xiong wrote:
> in some platforms, we found the max-read-request-size in Device Control
> Register is set to 0 by (BIOS?) during bootup, this will cause the
> performance(throughput) very bad.
> Restore it to a min-value.
> register definition of REG_DEVICE_CTRL is refined as well.
[...]
I'm guessing this memory-mapped register is an alias for the PCIe device
control register. I think you should be using pcie_set_readrq() to
ensure that the final setting conforms to the device's Max Payload Size
and system policy.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists