public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Steffen Persvold <sp@scali.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] BitKeeper tree for 2.4.x
Date: Mon, 14 Oct 2002 18:17:43 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805157@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805154@msgid-missing>

On Thu, 10 Oct 2002, Bjorn Helgaas wrote:

> NOTE: I removed the mmap support for MAP_WRITECOMBINED and
> MAP_NONCACHED to avoid issues with memory attribute aliasing.
> The only user of these that I know about is XFree86, which still
> seems functional when we ignore the attributes it requests.  I'm
> very interested in any problems caused by this change.
> 

Well, without MAP_WRITECOMBINED, streaming PIO accesses to the PCI bus 
drops from 330MByte/sec to approx. 100MByte/s using the Dolphin SCI card. 

This is an rather significant drop which makes the IA64 platform kind of 
uninteresting for high performance clustering (the Dolphin SCI cards are 
used for shared memory message passing between nodes).

We can of course hack this in for our usage (in our kernel driver) if you 
are totally against having it in the kernel headers, but I think since the 
hardware allows different mapping types, the kernel should take advantage 
of it.

Regards,
 -- 
  Steffen Persvold   |       Scali AS      
 mailto:sp@scali.com |  http://www.scali.com
Tel: (+47) 2262 8950 |   Olaf Helsets vei 6
Fax: (+47) 2262 8951 |   N0621 Oslo, NORWAY



  parent reply	other threads:[~2002-10-14 18:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 19:42 [Linux-ia64] BitKeeper tree for 2.4.x Bjorn Helgaas
2002-10-14 17:42 ` Bjorn Helgaas
2002-10-14 18:17 ` Steffen Persvold [this message]
2002-10-14 20:44 ` Grant Grundler
2002-10-17 16:46 ` Bjorn Helgaas
2002-10-17 18:16 ` Steffen Persvold
2002-10-17 18:31 ` Steffen Persvold
2002-10-17 19:38 ` Bjorn Helgaas
2002-10-17 21:53 ` Steffen Persvold
2002-10-17 22:10 ` Grant Grundler
2002-10-18  2:32 ` Steffen Persvold

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=marc-linux-ia64-105590709805157@msgid-missing \
    --to=sp@scali.com \
    --cc=linux-ia64@vger.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