public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
* [Linux-ia64] Re: Status on ioremap patch
@ 2001-09-14 23:14 David Mosberger
  2001-09-15 12:36 ` Steffen Persvold
                   ` (8 more replies)
  0 siblings, 9 replies; 12+ messages in thread
From: David Mosberger @ 2001-09-14 23:14 UTC (permalink / raw)
  To: linux-ia64

>>>>> On Fri, 14 Sep 2001 23:57:03 +0200, Steffen Persvold <sp@scali.no> said:

  Steffen> So, how about that patch guys ? Any chance you'll put it
  Steffen> into the mainstream IA64 kernel ???

I haven't looked at it yet, but am planning to do so as part of the
2.4.10 patch.

	--david


^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [Linux-ia64] Re: Status on ioremap patch
@ 2004-03-03 15:12 Hugo Kohmann
  2004-03-03 22:58 ` David Mosberger
  0 siblings, 1 reply; 12+ messages in thread
From: Hugo Kohmann @ 2004-03-03 15:12 UTC (permalink / raw)
  To: linux-ia64


Hi,

Is there any news or progress for official support for setting up kernel 
space write-combine mappings for Itanium systems. ?? Steffens patch is a 
good start, but we would like to avoid patching the kernel.

We are currently implementing a kernel space socket module for SCI 
(bypassing the TCP/IP protocols). Typical latency for send/receive 
between two systems is down to 2.7us for small messages ( Benchmarks 
running on Opterons ). Without kernel write-combine we would need to use 
regular DMA to move data, and we would no longer get the 2.7us latency.

Linux running on both IA32 and X86_64 systems supports some kind of kernel 
write-combine, why not IA64 ??

Best regards

Hugo



>>>>>> On Wed, 09 Jan 2002 21:01:13 +0100, Steffen Persvold <sp@scali.no> 
>said:
>
>  Steffen> So, what about this patch (posted earlier) David ? Have you
>  Steffen> seen the comments from Keith ?
>
>Keith's concerns are legitimate and to some degree apply even for
>ia64.  On ia64, we need to be careful to avoid mapping the same
>physical page with different memory attributes.  If more and more
>drivers are starting to use write-combine mappings, we need to solve
>this problem properly.  I don't have a solution off hand (I suspect
>we'll have to keep track of which i/o regions are mapped how) and
>don't have time to work on it now.  I'd recommend to maintain a
>separate patch for now, until a proper solution is ready (which will
>have to take non-ia64 platforms into consideration, of course).
>
>	--david
>
>PS: I apologize for not being as responsive yet as I'd like to be.
>    I'm done with the book (well, 99.999% as my wife put it...) and
>    ready to attack my backlog of kernel work (and other things, such
>    as user-level unwind support).  I just had a spell of bad luck
>    this week, which didn't help.  Hopefully, over the next one or two
>    weeks, things will start to go back to normal.




-- 

============================================Hugo Kohmann                           |
Dolphin Interconnect Solutions AS      | E-mail:
P.O. Box 150 Oppsal                    | hugo@dolphinics.com
N-0619 Oslo, Norway                    | Web:
Tel:+47 23 16 71 73                    | http://www.dolphinics.com
Fax:+47 23 16 71 80                    | Home Office:
Visiting Address: Olaf Helsets vei 6   | Tel: +47 22 23 25 35


^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2004-03-03 22:58 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-09-14 23:14 [Linux-ia64] Re: Status on ioremap patch David Mosberger
2001-09-15 12:36 ` Steffen Persvold
2001-09-28 12:39 ` Jes Sorensen
2002-01-05 15:01 ` Steffen Persvold
2002-01-05 23:30 ` Keith Owens
2002-01-06 11:02 ` Steffen Persvold
2002-01-06 11:55 ` Keith Owens
2002-01-06 14:27 ` Steffen Persvold
2002-01-09 20:01 ` Steffen Persvold
2002-01-10  3:01 ` David Mosberger
  -- strict thread matches above, loose matches on Subject: below --
2004-03-03 15:12 Hugo Kohmann
2004-03-03 22:58 ` David Mosberger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox