From: "David S. Miller" <davem@redhat.com>
To: kevin.vanmaren@unisys.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: With Daniel Phillips Patch
Date: Wed, 22 Aug 2001 19:26:00 -0700 (PDT) [thread overview]
Message-ID: <20010822.192600.35357607.davem@redhat.com> (raw)
In-Reply-To: <245F259ABD41D511A07000D0B71C4CBA289F30@us-slc-exch-3.slc.unisys.com>
In-Reply-To: <245F259ABD41D511A07000D0B71C4CBA289F30@us-slc-exch-3.slc.unisys.com>
From: "Van Maren, Kevin" <kevin.vanmaren@unisys.com>
Date: Wed, 22 Aug 2001 21:22:19 -0500
If the HW generates DAC for addresses < 4GB whenever enabling
support for 64-bit addresses, then that is very broken.
That is what happens.
Please don't complain that I didn't spend hours searching
through the archives looking for a message from months? years? ago
that I didn't know existed.
Weeks, if not days.
> I think for SAC-only devices, it is just dumb wasted space in the
> driver image.
Perhaps. But the question is whether it is simpler/better to have
HIGHMEM x86 kernels (which by definition have memory to spare) waste
a few bytes to provide "sane" interfaces across all platforms. And
whether the kernel bloat for all the additional functions compensates
for it ;-)
The plain fact is that %95 of PCI devices do not support DAC
addressing.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-08-23 2:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 2:22 With Daniel Phillips Patch Van Maren, Kevin
2001-08-23 2:26 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-23 1:06 Van Maren, Kevin
2001-08-23 1:31 ` David S. Miller
2001-08-23 1:40 ` Justin T. Gibbs
2001-08-23 1:45 ` David S. Miller
2001-08-22 6:46 With Daniel Phillips Patch (was: aic7xxx with 2.4.9 on 7899P) Jens Axboe
2001-08-22 13:24 ` Justin T. Gibbs
2001-08-22 15:05 ` With Daniel Phillips Patch David S. Miller
2001-08-22 18:21 ` Gérard Roudier
2001-08-22 18:32 ` David S. Miller
2001-08-22 18:32 ` Justin T. Gibbs
2001-08-22 18:46 ` David S. Miller
2001-08-22 19:41 ` Justin T. Gibbs
2001-08-22 20:19 ` David S. Miller
2001-08-22 21:07 ` Gérard Roudier
2001-08-22 21:14 ` David S. Miller
2001-08-22 21:14 ` David S. Miller
2001-08-22 21:40 ` Justin T. Gibbs
2001-08-22 23:09 ` David S. Miller
2001-08-23 0:01 ` Justin T. Gibbs
2001-08-23 0:40 ` David S. Miller
2001-08-23 0:55 ` Justin T. Gibbs
2001-08-23 1:03 ` Matthew Jacob
2001-08-23 1:08 ` David S. Miller
2001-08-23 1:32 ` Justin T. Gibbs
2001-08-23 1:39 ` David S. Miller
2001-08-23 1:49 ` Justin T. Gibbs
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=20010822.192600.35357607.davem@redhat.com \
--to=davem@redhat.com \
--cc=kevin.vanmaren@unisys.com \
--cc=linux-kernel@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