mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Jes Sorensen <jes@sunsite.dk>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	bcrl@redhat.com (Ben LaHaise),
	hiren_mehta@agilent.com ("MEHTA,HIREN (A-SanJose,ex1)"),
	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 achi ne
Date: Fri, 6 Jul 2001 16:46:45 -0700 (PDT)	[thread overview]
Message-ID: <15174.19941.681583.314691@pizda.ninka.net> (raw)
In-Reply-To: <d3d77ew5dd.fsf@lxplus015.cern.ch>
In-Reply-To: <15164.18270.460245.219060@pizda.ninka.net> <E15Fv14-0008TB-00@the-village.bc.nu> <15164.59159.645521.383074@pizda.ninka.net> <d3pubfw0fi.fsf@lxplus015.cern.ch> <15172.64662.696505.761486@pizda.ninka.net> <d3d77ew5dd.fsf@lxplus015.cern.ch>


Jes Sorensen writes:
 > David> And this still leaves the 64-bit dma_addr_t overhead issue.
 > 
 > The 64 bit dma_addr_t is only an issue on 32 bit architectures with
 > highmem enabled. I never suggested making dma_addr_t 64 bit on 32 bit
 > architectures as a general thing.

What about for drivers of SAC-only devices, they eat the overhead
when highmem is enabled too?

This says nothing about the real reason the IA64 solution is
unacceptable, the inputs to the mapping functions which must
be "page+offset+len" triplets as there is no logical "virtual
address" to pass into the mapping routines on 32-bit systems.

Face it, the ia64 stuff is not what we can use across the board.  It
simply doesn't deal with all the necessary issues.  Therefore,
encouraging driver author's to use this ia64 hacked up scheme is
not such a hot idea until we have a real API implemented.

Later,
David S. Miller
davem@redhat.com

  parent reply	other threads:[~2001-07-06 23:47 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-28 16:20 MEHTA,HIREN (A-SanJose,ex1)
2001-06-28 19:41 ` Jes Sorensen
2001-06-28 21:45 ` David S. Miller
2001-06-28 22:01 ` David S. Miller
2001-06-28 22:20   ` Jes Sorensen
2001-06-28 22:28     ` Alan Cox
2001-07-02  8:09       ` Jens Axboe
2001-06-28 22:24   ` Ben LaHaise
2001-07-02  8:09     ` Jens Axboe
2001-06-28 22:27   ` David S. Miller
2001-06-28 22:29   ` David S. Miller
2001-06-28 22:31     ` Ben LaHaise
2001-06-28 22:40       ` (reposting) how to get DMA'able memory within 4GB on 64-bit m Alan Cox
2001-06-28 22:38     ` (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne 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 [this message]
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
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

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=15174.19941.681583.314691@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bcrl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®