From: Roland Dreier <rdreier@cisco.com>
To: ebiederm@xmission.com (Eric W. Biederman), linux-kernel@vger.kernel.org
Cc: mst@mellanox.co.il, jackm@mellanox.co.il, ak@suse.de
Subject: pgprot_writecombine() and PATs on x86
Date: Wed, 25 Apr 2007 11:02:26 -0700 [thread overview]
Message-ID: <ada1wi8xrgt.fsf@cisco.com> (raw)
Hi Eric,
Where do your patches to add an implementation of
pgprot_writecombine() using PATs on x86 stand? The mlx4 driver I'm
planning on merging for 2.6.22 would really like writecombining, and
I'm interested in doing the work to finally get the PAT stuff merged
(probably for 2.6.23 I guess).
Just to give a little background on my motivation: the mlx4 hardware
allows a page in its PCI space to be mapped, where the driver can write
descriptors and payloads directly, instead of ringing a doorbell and
having the HW fetch the descriptor from system memory, for better latency.
The driver allows this page to be mapped to userspace and used
directly from latency sensitive stuff like MPI applications. I added
a hacked up version of the PAT stuff to map the page into userspace
with pgprot_writecombine(), and that lowered the measured MPI latency
by 450 nsecs, which doesn't seem like much until I tell you that the
latency when from ~1.85 usec to ~1.4 usec. So copying the descriptor
is a huge part of the total latency and users are definitely going to
want that 25% improvement.
Anyway as I said I want to get the PAT stuff upstream, so I'm posting
this to find out the latest state and avoid duplicating work.
Thanks,
Roland
next reply other threads:[~2007-04-25 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 18:02 Roland Dreier [this message]
2007-04-25 18:19 ` pgprot_writecombine() and PATs on x86 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
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=ada1wi8xrgt.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=jackm@mellanox.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@mellanox.co.il \
/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