From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Ram Pai <linuxram@us.ibm.com>, yinghai@kernel.org
Cc: jbarnes@virtuousgeek.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] PCI: fix cardbus and sriov regressions
Date: Sat, 25 Jun 2011 13:35:36 +0200 [thread overview]
Message-ID: <4E05C808.3060609@hartkopp.net> (raw)
In-Reply-To: <20110624192903.GM22917@ram-laptop>
On 24.06.2011 21:29, Ram Pai wrote:
> On Thu, Jun 23, 2011 at 04:55:06PM +0200, Oliver Hartkopp wrote:
>> Hello RP,
>>
>> unfortunately i noticed the discussion on linux-kernel ML a bit late, as i did
>> not subscribe it due to the traffic.
>
> sorry, did not see this mail earlier.
>
>
>>>>> When comparing the logs with mgdiff, i found
>>>>>
>>>>> in revered:
>>>>>
>>>>> pci_bus 0000:04: resource 0 [io 0x2000-0x20ff]
>>>>> pci_bus 0000:04: resource 1 [io 0x2400-0x24ff]
>>>>>
>>>>> in the fixed version (4 patches)
>>>>>
>>>>> pci_bus 0000:04: resource 0 [io 0x2400-0x24ff]
>>>>> pci_bus 0000:04: resource 1 [io 0x2001-0x2100]
>>
>> Did you get further with the unusual alignment?
>
> No. i was thinking this alignment should be ok, since that cardbus resource
> has to be SIZE aligned and not START aligned.
>
> However if it is not acceptable, i will figure out a way
> to get it aligned on the right boundaries.
I'm not sure how drivers expect to access the register layouts of their
specific hardware. E.g. if you have a 32-bit register at the beginning of the
io resource and the driver accesses this with a 32-bit write operation, the
misalignment would be handled (by the CPU) very expensive at runtime, which is
definitely a big drawback in performance. I know the networking people
re-arranging structs to get less cycles in accessing data structures ...
I tried to understand the reason for the original commit in 3.0.0-rc1 that
broke my system - very ambitious :-)
But IMHO you should meet analogue starting boundaries as we had before to make
sure that you don't brake things on machines that did not show up yet.
Best regards,
Oliver
next prev parent reply other threads:[~2011-06-25 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1308561849-3223-1-git-send-email-linuxram@us.ibm.com>
[not found] ` <4DFFB6B0.6090307@hartkopp.net>
[not found] ` <4DFFB945.5090203@hartkopp.net>
[not found] ` <20110620214127.GA22917@ram-laptop>
[not found] ` <4DFFC2FC.5050502@hartkopp.net>
2011-06-23 14:55 ` [PATCH 0/4] PCI: fix cardbus and sriov regressions Oliver Hartkopp
2011-06-24 19:29 ` Ram Pai
2011-06-25 11:35 ` Oliver Hartkopp [this message]
2011-06-27 17:34 ` Bjorn Helgaas
2011-06-20 22:47 Ram Pai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E05C808.3060609@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox