From: "David S. Miller" <davem@redhat.com>
To: kanoj@google.engr.sgi.com
Cc: sct@redhat.comsct@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,
alan@lxorguk.ukuu.org.uk
Subject: Re: pte_pagenr/MAP_NR deleted in pre6
Date: Thu, 17 Aug 2000 12:01:49 -0700 [thread overview]
Message-ID: <200008171901.MAA23835@pizda.ninka.net> (raw)
In-Reply-To: <200008171907.MAA37675@google.engr.sgi.com> (message from Kanoj Sarcar on Thu, 17 Aug 2000 12:07:12 -0700 (PDT))
Whatever you do, you either have to introduce paddr_t (which to me
seems more intuitive) or page_to_pfn. We can argue one way or
another, but paddr_t might give you type checking for free too ...
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.
The next gripe is that it will make many clueless driver
etc. developers (who don't read documentation even, but write a large
portion of the vendor Linux drivers :-) will try to do things
like "void *p = (void *) (PAGE_OFFSET + x->paddr);" and expect
this to work, or maybe they'll even pass it to virt_to_bus or similar.
If people don't think these two things will be an issue, fine with
me. :-)
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.
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:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-10 17:18 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 [this message]
2000-08-17 19:19 ` Alan Cox
2000-08-17 19:20 ` David S. Miller
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=200008171901.MAA23835@pizda.ninka.net \
--to=davem@redhat.com \
--cc=kanoj@google.engr.sgi.com \
--cc=sct@redhat.comsct \
/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