public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: David Mosberger <davidm@hpl.hp.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Arjan van de Ven <arjanv@redhat.com>,
	linux-kernel@vger.kernel.org, linux-ia64@linuxia64.org,
	marcelo@conectiva.com.br, davem@redhat.com
Subject: Re: [Linux-ia64] patch to no longer use ia64's software mmu
Date: Tue, 4 Dec 2001 11:32:43 -0500	[thread overview]
Message-ID: <20011204113243.B5075@devserv.devel.redhat.com> (raw)
In-Reply-To: <15371.62205.231945.798891@napali.hpl.hp.com> <E16BC09-0001Ql-00@the-village.bc.nu> <15372.63827.716885.948119@napali.hpl.hp.com>
In-Reply-To: <15372.63827.716885.948119@napali.hpl.hp.com>; from davidm@hpl.hp.com on Tue, Dec 04, 2001 at 08:26:59AM -0800

On Tue, Dec 04, 2001 at 08:26:59AM -0800, David Mosberger wrote:
> >>>>> On Tue, 4 Dec 2001 09:36:33 +0000 (GMT), Alan Cox <alan@lxorguk.ukuu.org.uk> said:
> 
>   >> Another concern I have is that, fundamentally, I dislike the idea
>   >> of penalizing all IA-64 platforms due to one chipset that is,
>   >> shall we say, "lacking" (i.e., doesn't have an I/O TLB).
> 
>   Alan> Allow me to introduce to you the concept of CONFIG_ options 8)
>   Alan> It makes a lot of sense to have a generic IA64 kernel, and an
>   Alan> IA64 designed by people with a brain kernel.
> 
> I think the issue at hand is whether, longer term, it is desirable to
> move all bounce buffer handling into the PCI DMA layer or whether
> Linux should continue to make bounce buffer management visible to
> drivers.  I'd be interested in hearing opinions.

For "lacking" architectures (current ia64 machines, x86 with pae36) the only
real performing solution is to bounce in subsystems (not low level drivers).
The PCI layer doesn't have enough scope to decide what to do...

  reply	other threads:[~2001-12-04 16:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 21:00 patch to no longer use ia64's software mmu Arjan van de Ven
2001-12-03 21:47 ` [Linux-ia64] " David Mosberger
2001-12-03 21:53   ` Arjan van de Ven
2001-12-04  9:36   ` Alan Cox
2001-12-04 16:26     ` David Mosberger
2001-12-04 16:32       ` Arjan van de Ven [this message]
2001-12-04 17:18       ` Alan Cox
2001-12-04 17:43         ` David Mosberger
2001-12-04 17:59           ` Alan Cox
2001-12-04 18:06             ` David Mosberger
2001-12-04 18:19               ` Alan Cox
2001-12-04 18:14                 ` David Mosberger
2001-12-04 20:22       ` David S. Miller
2001-12-04 20:32         ` David Mosberger
2001-12-04 14:25 ` Andreas Schwab

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=20011204113243.B5075@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=linux-ia64@linuxia64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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