public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sunsite.dk>
To: "David S. Miller" <davem@redhat.com>
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: 05 Jul 2001 23:06:25 +0200	[thread overview]
Message-ID: <d3pubfw0fi.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: <15164.18270.460245.219060@pizda.ninka.net> <E15Fv14-0008TB-00@the-village.bc.nu> <15164.59159.645521.383074@pizda.ninka.net>
In-Reply-To: "David S. Miller"'s message of "Fri, 29 Jun 2001 13:37:43 -0700 (PDT)"

>>>>> "David" == David S Miller <davem@redhat.com> writes:

David> Alan Cox writes:
>> Thats something we already know has to be fixed. Its true with or
>> without an IOMMU that there may be cases where there is no free
>> mapping space

David> True, but my intended point is that starving the SAC-only users
David> then returning DAC addresses to DAC-capable devices is just as
David> unacceptable.

David> When we have one of these compute cluster cards in the box, and
David> Jes's suggested algorithm is used, the rest of the SAC devices
David> in the box would be totally screwed once the IOMMU fills up.

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.

Cheers
Jes

  reply	other threads:[~2001-07-05 21:07 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 [this message]
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
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=d3pubfw0fi.fsf@lxplus015.cern.ch \
    --to=jes@sunsite.dk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bcrl@redhat.com \
    --cc=davem@redhat.com \
    --cc=hiren_mehta@agilent.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