From: "David S. Miller" <davem@redhat.com>
To: alan@lxorguk.ukuu.org.uk
Cc: kanoj@google.engr.sgi.com, sct@redhat.com, roman@augan.com,
linux-mm@kvack.org, linux-kernel@vger.rutgers.edu,
rmk@arm.linux.org.uk, nico@cam.org, davidm@hpl.hp.com
Subject: Re: pte_pagenr/MAP_NR deleted in pre6
Date: Thu, 17 Aug 2000 12:20:50 -0700 [thread overview]
Message-ID: <200008171920.MAA23931@pizda.ninka.net> (raw)
In-Reply-To: <E13PVCr-0003Vf-00@the-village.bc.nu> (message from Alan Cox on Thu, 17 Aug 2000 20:19:59 +0100 (BST))
> My only two gripes about paddr_t is that long long is not only
> expensive but has been also known to be buggy on 32-bit platforms.
Except for the x86 36bit abortion do we need a long long paddr_t on any
32bit platform ?
Sparc32, mips32...
> Which reminds me, we need to schedule a field day early 2.5.x where
> virt_to_bus and bus_to_virt are exterminated, this is the only way we
> can move to drivers using page+offset correctly, forcing them through
> interface such as the pci_dma API instead.
So you'll be adding an isa_alloc_consistant, mca_alloc_consistent,
m68k_motherboard_alloc_consistent , ....
I'll probably be adding isa_virt_to_bus, because when it is in fact
"ISA like" the driver already knows that it must be certain that the
physical address is below the 16MB mark right? Then the cases left on
x86 are MCA (which can use the ISA interface) and PCI drivers which
must be updated to use the PCI dma API.
Just like I did for SBUS, the m68k folks can deal with their issues
any way they like.
Its not trivial to exterminate.
I think it is. What's not trivial is getting bozos to clean up their
drivers. For example, BTTV still doesn't use the PCI dma stuff simply
because nobody wishes to use their brains a little bit and encapsulate
the user DMA stuff into a common spot (it's duplicated in 4 or 5
drivers) which uses scatter gather lists with the DMA api.
Later,
David S. Miller
davem@redhat.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-08-17 19:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-10 17:18 pte_pagenr/MAP_NR deleted in pre6 Kanoj Sarcar
2000-08-11 2:24 ` David S. Miller
2000-08-14 0:34 ` Anton Blanchard
2000-08-11 11:50 ` Roman Zippel
2000-08-11 13:20 ` Russell King
2000-08-11 14:56 ` Roman Zippel
2000-08-12 9:18 ` Bjorn Wesen
2000-08-11 17:21 ` Kanoj Sarcar
2000-08-14 9:29 ` Roman Zippel
2000-08-15 16:19 ` Stephen C. Tweedie
2000-08-16 8:25 ` Roman Zippel
2000-08-16 17:13 ` Kanoj Sarcar
2000-08-16 18:20 ` Stephen C. Tweedie
2000-08-16 18:24 ` David S. Miller
2000-08-16 19:53 ` Stephen C. Tweedie
2000-08-16 18:47 ` Kanoj Sarcar
2000-08-16 18:39 ` David S. Miller
2000-08-16 19:30 ` Stephen C. Tweedie
2000-08-16 22:22 ` Kanoj Sarcar
2000-08-17 9:11 ` Stephen C. Tweedie
2000-08-17 19:07 ` Kanoj Sarcar
2000-08-17 19:01 ` David S. Miller
2000-08-17 19:19 ` Alan Cox
2000-08-17 19:20 ` David S. Miller [this message]
2000-08-17 19:33 ` Alan Cox
2000-08-17 19:36 ` Kanoj Sarcar
2000-09-07 14:31 ` Ralf Baechle
2000-08-17 19:50 ` Kanoj Sarcar
2000-08-17 19:41 ` David S. Miller
2000-09-07 14:26 ` Ralf Baechle
2000-08-17 19:56 ` Alan Cox
2000-08-17 19:24 ` Alan Cox
2000-08-17 19:32 ` Kanoj Sarcar
2000-08-17 19:30 ` David S. Miller
2000-08-17 20:00 ` Kanoj Sarcar
2000-08-16 18:17 ` Stephen C. Tweedie
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=200008171920.MAA23931@pizda.ninka.net \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidm@hpl.hp.com \
--cc=kanoj@google.engr.sgi.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=nico@cam.org \
--cc=rmk@arm.linux.org.uk \
--cc=roman@augan.com \
--cc=sct@redhat.com \
/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