public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: pgprot_writecombine & shub 1.x
Date: Wed, 12 Jan 2005 21:54:51 +0000	[thread overview]
Message-ID: <16869.40107.667336.912445@napali.hpl.hp.com> (raw)
In-Reply-To: <200501111200.02504.jbarnes@sgi.com>

>>>>> On Wed, 12 Jan 2005 20:31:30 +0100 (CET), Hugo Kohmann <hugo@dolphinics.no> said:

  Hugo> Is there any new plans to implement support for writecombine
  Hugo> in kernel space ?

I don't know of anybody who's working on it at the moment.

  Hugo> We have implemented a new socket transport family, AF_SCI,
  Hugo> that provides UDP/TCP compliant transport over SCI that needs
  Hugo> writecombine to archieve max througpht and low latency for
  Hugo> small messages. Large messages can be send using DMA, but
  Hugo> small messages highly benefit from memory mapped
  Hugo> transmission....

I think there are two somewhat separate issues here:

 (1) WC mapping of uncachable address-ranges.
 (2) WC mapping of memory.

(1) isn't much of an issue (at least for today's chips; I think we may
still be violating the architecture if we end up mapping the same
address-range both UC and WC, but current chips don't care, AFAIK).

(2) is where things get trickier.  You'd have to make sure that any
memory that's mapped WC is allocated in granule-sized chunks.  There
is no support for this at the moment.  I do think it might be
worthwhile to support this, but don't know of anybody working on it.

	--david

  parent reply	other threads:[~2005-01-12 21:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 20:00 pgprot_writecombine & shub 1.x Jesse Barnes
2005-01-11 22:12 ` David Mosberger
2005-01-11 22:35 ` Jesse Barnes
2005-01-12 18:51 ` Jim Hull
2005-01-12 19:31 ` Hugo Kohmann
2005-01-12 19:32 ` Jesse Barnes
2005-01-12 21:54 ` David Mosberger [this message]
2005-01-19 17:28 ` Jesse Barnes
2005-01-19 17:53 ` David Mosberger
2005-01-19 17:56 ` Jesse Barnes
2005-01-19 18:04 ` David Mosberger
2005-01-19 18:16 ` Luck, Tony
2005-01-19 18:21 ` Jesse Barnes
2005-01-19 18:38 ` Luck, Tony
2005-01-19 19:33 ` Bjorn Helgaas
2005-01-19 21:51 ` Jesse Barnes
2005-01-19 22:00 ` Luck, Tony
2005-01-19 22:03 ` Jesse Barnes
2005-01-19 22:07 ` David Mosberger
2005-01-19 22:16 ` Jesse Barnes
2005-01-19 22:20 ` David Mosberger
2005-01-19 22:22 ` Jesse Barnes
2005-01-19 22:25 ` David Mosberger
2005-01-19 22:36 ` Jesse Barnes
2005-01-19 22:39 ` David Mosberger
2005-01-19 22:53 ` Jesse Barnes
2005-01-20  9:03 ` Jes Sorensen
2005-01-20 13:43 ` Hugo Kohmann
2005-01-20 16:42 ` Jesse Barnes
2005-01-20 16:45 ` Jesse Barnes
2005-01-20 17:17 ` David Mosberger
2005-01-21  9:00 ` Jes Sorensen
2005-01-21  9:01 ` Jes Sorensen

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=16869.40107.667336.912445@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.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