From: Steffen Persvold <sp@scali.no>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Write Combining (Write Coalescing) on memory mapped
Date: Mon, 10 Sep 2001 14:16:31 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805151@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805106@msgid-missing>
Steffen Persvold wrote:
>
> David Mosberger wrote:
> >
> > >>>>> On Sat, 25 Aug 2001 16:40:24 +0200, Steffen Persvold <sp@scali.no> said:
> >
> > Steffen> Just a repost since I didn't get any feedback. I've also
> > Steffen> copied some auhtors I found in asm/io.h. I appologize for
> > Steffen> any inconvenience, but this issue is quite important to us.
> >
> > I didn't see anything fundamentally wrong with what you're trying to
> > do, but I haven't looked at the code. Some debugging may be called
> > for.
> >
>
> Do you think it's easier to set up a region which is mapped all the time, so
> that ioremap_nocache() uses the already defined region 6 for uncached accesses
> and ioremap() uses this new region with "Write Coalescing" enabled ? How should
> I proceed to introduce such a region ?
>
I haven't received any response. Does that mean that you guys don't even care
about this issue ??
Regards,
--
Steffen Persvold | Scali Computer AS | Try out the world's best
mailto:sp@scali.no | http://www.scali.com | performing MPI implementation:
Tel: (+47) 2262 8950 | Olaf Helsets vei 6 | - ScaMPI 1.12.2 -
Fax: (+47) 2262 8951 | N0621 Oslo, NORWAY | >300MBytes/s and <4uS latency
next prev parent reply other threads:[~2001-09-10 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 0:24 [Linux-ia64] Re: Write Combining (Write Coalescing) on memory mapped I/O on IA64 David Mosberger
2001-08-30 6:39 ` Steffen Persvold
2001-09-10 14:16 ` Steffen Persvold [this message]
2001-09-10 14:51 ` [Linux-ia64] Re: Write Combining (Write Coalescing) on memory mapped David Mosberger
2001-09-10 15:26 ` Steffen Persvold
2001-09-10 15:49 ` David Mosberger
2001-09-10 19:29 ` 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-105590698805151@msgid-missing \
--to=sp@scali.no \
--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