From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "David S. Miller" <davem@redhat.com>,
Ben LaHaise <bcrl@redhat.com>, Jes Sorensen <jes@sunsite.dk>,
"MEHTA,HIREN (A-SanJose,ex1)" <hiren_mehta@agilent.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: (reposting) how to get DMA'able memory within 4GB on 64-bit m
Date: Sat, 07 Jul 2001 08:17:53 -0400 [thread overview]
Message-ID: <3B46FDF1.A38E5BB6@mandrakesoft.com> (raw)
In-Reply-To: <E15Iqqm-0005jr-00@the-village.bc.nu>
Alan Cox wrote:
>
> > > that the expected lifespan for 32 bit systems is now less than 3 years, so
> > > elaborate planning that delays implementation buys us nothing more than a
> > > smaller window of usefulness.
> > Maybe by then only 64-bit cpus will matter. Who knows.
>
> Reality check.
>
> Embedded PCI 32bit processors are going to be very common
> People are only now retiring 486's
>
> So add another seven or eight years to your estimate
Given a little more context, I thought we were talking specifically
about 64bit-PCI-on-32bit-machines?
Assuming that, AFAICS Ben's statement seems more correct.
And IMHO we definitely should not optimize for 64-bit-on-32-bit case.
Let CONFIG_HIGHMEM grow dma_addr_t to 64-bits, for that case only...
--
Jeff Garzik | A recent study has shown that too much soup
Building 1024 | can cause malaise in laboratory mice.
MandrakeSoft |
next prev parent reply other threads:[~2001-07-07 12:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 16:20 (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne MEHTA,HIREN (A-SanJose,ex1)
2001-06-28 19:41 ` Jes Sorensen
2001-06-28 22:01 ` David S. Miller
2001-06-28 22:20 ` Jes Sorensen
2001-06-28 22:27 ` David S. Miller
2001-06-28 22:28 ` Alan Cox
2001-07-02 8:09 ` Jens Axboe
2001-06-28 22:24 ` Ben LaHaise
2001-06-28 22:29 ` David S. Miller
2001-06-28 22:31 ` Ben LaHaise
2001-06-28 22:38 ` David S. Miller
2001-06-28 22:45 ` Ben LaHaise
2001-06-28 22:48 ` David S. Miller
2001-06-28 22:48 ` (reposting) how to get DMA'able memory within 4GB on 64-bit m Alan Cox
2001-06-28 22:55 ` (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne Jes Sorensen
2001-06-29 9:16 ` David S. Miller
2001-06-29 9:56 ` Alan Cox
2001-06-29 20:37 ` David S. Miller
2001-07-05 21:06 ` Jes Sorensen
2001-07-05 23:47 ` David S. Miller
2001-07-05 23:50 ` Ben LaHaise
2001-07-06 13:31 ` Jes Sorensen
2001-07-06 23:46 ` David S. Miller
2001-07-07 3:58 ` Ben LaHaise
2001-07-07 5:35 ` David S. Miller
2001-07-07 12:06 ` (reposting) how to get DMA'able memory within 4GB on 64-bit m Alan Cox
2001-07-07 12:17 ` Jeff Garzik [this message]
2001-07-07 12:21 ` Alan Cox
2001-07-07 13:00 ` David S. Miller
2001-07-11 19:16 ` Jes Sorensen
2001-07-11 21:54 ` Chris Wedgwood
2001-07-11 23:17 ` David S. Miller
2001-07-11 23:07 ` David S. Miller
2001-06-28 22:40 ` Alan Cox
2001-07-02 8:09 ` (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne Jens Axboe
2001-06-28 21:45 ` David S. Miller
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=3B46FDF1.A38E5BB6@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@redhat.com \
--cc=davem@redhat.com \
--cc=hiren_mehta@agilent.com \
--cc=jes@sunsite.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.