From: Roland Dreier <rdreier@cisco.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [v2.6.26] what's brewing in x86.git for v2.6.26
Date: Wed, 16 Apr 2008 13:37:30 -0700 [thread overview]
Message-ID: <adar6d5ilit.fsf@cisco.com> (raw)
In-Reply-To: <20080416202338.GA6007@elte.hu> (Ingo Molnar's message of "Wed, 16 Apr 2008 22:23:38 +0200")
> - PAT support - first step towards phasing out MTRR's for cache
> attribute control
I just grabbed your tree and I see that there is no
pgprot_writecombine() for x86. I see that pci_mmap_page_range() handles
write combining but there's no way for a PCI driver to allow userspace
to mmap() part of a BAR with WC enabled. Doing this gives a big
performance boost for running low-latency apps on InfiniBand hardware
driven by the mlx4 driver (look for the FIXME about it in
drivers/infiniband/hw/mlx4/main.c). Are there any plans to handle this
somehow?
Thanks,
Roland
next prev parent reply other threads:[~2008-04-16 20:37 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 20:23 [v2.6.26] what's brewing in x86.git for v2.6.26 Ingo Molnar
2008-04-16 20:37 ` Roland Dreier [this message]
2008-04-16 22:18 ` Suresh Siddha
2008-04-16 20:50 ` Andi Kleen
2008-04-17 10:06 ` Alexander van Heukelum
2008-04-17 10:51 ` Andi Kleen
2008-04-17 13:33 ` Alexander van Heukelum
2008-04-18 8:38 ` Ingo Molnar
2008-04-18 10:51 ` Andi Kleen
2008-04-17 7:25 ` Andrew Morton
2008-04-17 7:45 ` Pekka Enberg
2008-04-17 8:20 ` Andrew Morton
2008-04-17 8:32 ` Pekka J Enberg
2008-04-17 8:34 ` Pekka Enberg
2008-04-17 8:40 ` Ingo Molnar
2008-04-17 8:42 ` Andrew Morton
2008-04-17 11:49 ` Christoph Hellwig
2008-04-17 11:56 ` Ingo Molnar
2008-04-17 18:01 ` Andrew Morton
2008-04-17 18:51 ` Ingo Molnar
2008-04-17 19:57 ` Andrew Morton
2008-04-17 20:18 ` Ingo Molnar
2008-04-18 9:33 ` Tomasz Kłoczko
2008-04-18 9:42 ` Ingo Molnar
2008-04-17 8:14 ` Andrew Morton
2008-04-17 8:57 ` Avi Kivity
2008-04-17 10:32 ` Johannes Weiner
2008-04-17 10:50 ` Andrew Morton
2008-04-17 11:49 ` Christoph Hellwig
2008-04-17 17:36 ` Andrew Morton
2008-04-17 8:30 ` Ingo Molnar
2008-04-17 8:40 ` Andrew Morton
2008-04-17 8:45 ` David Miller
2008-04-17 8:54 ` Andrew Morton
2008-04-17 8:56 ` Andrew Morton
2008-04-17 9:19 ` David Miller
2008-04-17 9:33 ` Andrew Morton
2008-04-17 9:06 ` Ingo Molnar
2008-04-17 9:18 ` Andrew Morton
2008-04-17 9:30 ` Ingo Molnar
2008-04-17 9:36 ` Andrew Morton
2008-04-17 9:46 ` Ingo Molnar
2008-04-17 10:06 ` Andrew Morton
2008-04-17 10:11 ` Andi Kleen
2008-04-17 10:18 ` Andrew Morton
2008-04-17 10:29 ` Andi Kleen
2008-04-17 10:19 ` Pekka Enberg
2008-04-17 10:33 ` Andrew Morton
2008-04-17 10:38 ` Ingo Molnar
2008-04-17 10:42 ` Pekka Enberg
2008-04-18 11:12 ` Nick Piggin
2008-04-17 14:01 ` Arjan van de Ven
2008-04-17 15:26 ` Ingo Molnar
2008-04-18 12:41 ` Ingo Molnar
2008-04-17 10:41 ` Pekka Enberg
2008-04-17 18:47 ` Vegard Nossum
2008-04-17 19:27 ` Ingo Molnar
2008-04-17 19:35 ` Ingo Molnar
2008-04-17 19:39 ` Vegard Nossum
2008-04-17 19:43 ` Andrew Morton
2008-04-17 20:39 ` Vegard Nossum
2008-04-17 20:55 ` Andrew Morton
2008-04-17 9:53 ` Andrew Morton
2008-04-17 7:48 ` Andrew Morton
2008-04-18 6:27 ` Andrew Morton
2008-04-18 6:38 ` David Miller
2008-04-18 7:47 ` Ingo Molnar
2008-04-18 8:00 ` Andrew Morton
2008-04-18 8:11 ` Christoph Hellwig
2008-04-18 8:18 ` David Miller
2008-04-18 12:48 ` Ingo Molnar
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=adar6d5ilit.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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