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: Thu, 5 Jul 2001 16:47:34 -0700 (PDT)	[thread overview]
Message-ID: <15172.64662.696505.761486@pizda.ninka.net> (raw)
In-Reply-To: <d3pubfw0fi.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>


Jes Sorensen writes:
 > The dma_mask in struct pci_dev tells you whether you are DAC
 > capable. We pass a pointer to this struct when we call the pci_*
 > functions so the required information needed to make the decision
 > whether to return a SAC or a DAC address is already available.

The decision is not based upon "device capable of DAC", that is
precisely my point.

The decision must be based upon a number of considerations.

1) Can it do DAC

2) Is DAC more efficient than SAC on this platform

3) Does the devices _need_ DAC even if it is slower because
   it requires referencing large portions of the DMA
   address space simultaneously

Sure, you could imply all of this complexity in the driver
by making them consider all of these issues when setting the
mask, but that isn't a nice interface at all.

And this still leaves the 64-bit dma_addr_t overhead issue.

Later,
David S. Miller
davem@redhat.com

  parent reply	other threads:[~2001-07-05 23:48 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 [this message]
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
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=15172.64662.696505.761486@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®