From: ebiederm@xmission.com (Eric W. Biederman)
To: Roland Dreier <rdreier@cisco.com>
Cc: Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, mst@mellanox.co.il,
jackm@mellanox.co.il
Subject: Re: pgprot_writecombine() and PATs on x86
Date: Wed, 25 Apr 2007 12:45:51 -0600 [thread overview]
Message-ID: <m11wi8s36o.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <adaodlcwbdo.fsf@cisco.com> (Roland Dreier's message of "Wed, 25 Apr 2007 11:35:15 -0700")
Roland Dreier <rdreier@cisco.com> writes:
> > Roland is the mlx4 sane enough to put the memory that needs
> > write-combining a prefetchable bar. So several cards can be combined
> > together?
>
> Yes, it is in a prefetchable BAR. It's the second half of the second
> BAR in:
>
> 0d:00.0 InfiniBand: Mellanox Technologies Unknown device 634a (rev a0)
> Subsystem: Mellanox Technologies Unknown device 634a
> Flags: bus master, fast devsel, latency 0, IRQ 16
> Memory at fc400000 (64-bit, non-prefetchable) [size=1M]
> Memory at d8000000 (64-bit, prefetchable) [size=8M]
> Memory at fc3fe000 (64-bit, non-prefetchable) [size=8K]
> Capabilities: <access denied>
>
> but I'm not sure what you mean about combining several cards?
So in general the pci prefetchable attribute means write-combining as
well as prefetching is safe. A sane BIOS will allocate prefetchable
BARS contiguously in the address space. So on a good day you
can just use one MTRR to map all of the prefetchable BARs as write-combining.
Eric
next prev parent reply other threads:[~2007-04-25 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 18:02 Roland Dreier
2007-04-25 18:19 ` Andi Kleen
2007-04-25 18:31 ` Eric W. Biederman
2007-04-25 18:35 ` Roland Dreier
2007-04-25 18:45 ` Eric W. Biederman [this message]
2007-04-26 5:43 ` Michael S. Tsirkin
2007-04-26 6:13 ` Eric W. Biederman
2007-04-25 18:33 ` Roland Dreier
2007-04-25 18:41 ` Dave Jones
2007-04-25 19:10 ` Andi Kleen
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=m11wi8s36o.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=jackm@mellanox.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@mellanox.co.il \
--cc=rdreier@cisco.com \
/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
Powered by JetHome