All of lore.kernel.org
 help / color / mirror / Atom feed
From: Terence Ripperda <tripperda@nvidia.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: tripperda@nvidia.com
Subject: Re: 2.6.10-rc2-mm4
Date: Fri, 3 Dec 2004 15:59:27 -0600	[thread overview]
Message-ID: <20041203215927.GE1709@hygelac> (raw)


(sorry for breaking the email thread, I tried to grab the mbox archive
for responding, but ftp.uwsg.iu.edu seems to be having problems with
the mail archive).

in response to Alan Cox' voiced concerns from Tue Nov 30:

> That would also be a proprietary hook wouldn't it 8)

nvidia really isn't interested in proprietary hooks; such a hook
really wouldn't be good for nvidia or the linux kernel. but we don't
feel that a 32-bit zone is such a hook.

> beyond the supported open source hardware PCI-Express is the
> non-AGPGART user and that is 64bit.

I assume you mean traditional pci in this case, but I remain confused.
the pci spec calls for 32-bits of addressing, although there is an
optional extension for 64-bit bus extension pins. I can't speak for other
pci devices, but all of our pci devices are 32-bit.

additionally, the pci-express spec defines legacy and non-legacy
devices.  legacy devices are only required to address 32-bits, whereas
non-legacy devices are required to handle 64-bit addresses.

> In the video space it's even stranger because DRI doesn't need it

I'm unclear how traditional pci video cards function without being
able to allocate < 32-bit addresses for dma purposes. are the video cards
you've tested 64-bit capable or is dma disabled? what about 32-bit cards? I'm
afraid I don't understand how this isn't an issue.

> it seems a risky path because of the past problems trying to get
> zone balancing working.

I certainly understand the concerns with this, although I was led to
believe that recent 2.6 work made the zone balancing much less
expensive.  is that not the case?

> I can find users for a 512Mb or 1Gb DMA region

there was some brief discussion of this when we originally discussed
32-bit addressing issues, but I don't know if a satisfactory solution was
reached.  If a 1Gb region was prefered for this reason, that should satisfy
nvidia's needs for 32-bit addressing, but I couldn't speak for any other device
drivers.

for reference, the previous discussion was here:

http://www.uwsg.indiana.edu/hypermail/linux/kernel/0406.2/2093.html

Thanks,
Terence



             reply	other threads:[~2004-12-03 21:59 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03 21:59 Terence Ripperda [this message]
2004-12-05 19:46 ` 2.6.10-rc2-mm4 Alan Cox
     [not found] <41BF2332.mailL911D9Q6T@suse.de.suse.lists.linux.kernel>
2004-12-14 19:00 ` 2.6.10-rc2-mm4 Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2004-11-30 18:29 2.6.10-rc2-mm4 Petr Vandrovec
2004-11-30 18:38 ` 2.6.10-rc2-mm4 Alan Cox
2004-11-30 17:50 2.6.10-rc2-mm4 Andrew Morton
2004-11-30 18:06 ` 2.6.10-rc2-mm4 Arjan van de Ven
2004-11-30 18:21   ` 2.6.10-rc2-mm4 Andrew Morton
2004-11-30 18:25     ` 2.6.10-rc2-mm4 Arjan van de Ven
2004-11-30 18:32       ` 2.6.10-rc2-mm4 Andrew Morton
2004-11-30 17:44         ` 2.6.10-rc2-mm4 Alan Cox
2004-11-30 19:46           ` 2.6.10-rc2-mm4 Andrew Morton
2004-11-30 19:36         ` 2.6.10-rc2-mm4 Arjan van de Ven
2004-11-30 18:48       ` 2.6.10-rc2-mm4 William Lee Irwin III
2004-12-02  8:03         ` 2.6.10-rc2-mm4 Jes Sorensen
2004-12-02  8:01     ` 2.6.10-rc2-mm4 Jes Sorensen
2004-11-30 18:31   ` 2.6.10-rc2-mm4 Christoph Hellwig
2004-11-30 18:38     ` 2.6.10-rc2-mm4 Alan Cox
2004-11-30 18:30 ` 2.6.10-rc2-mm4 Christoph Hellwig
2004-11-30 19:18 ` 2.6.10-rc2-mm4 Stephen Smalley
2004-11-30 19:29   ` 2.6.10-rc2-mm4 Chris Wright
2004-11-30 19:43     ` 2.6.10-rc2-mm4 Christoph Hellwig
2004-11-30 19:55       ` 2.6.10-rc2-mm4 Jeff Mahoney
2004-12-01 23:32       ` 2.6.10-rc2-mm4 Jeffrey Mahoney
2004-12-02  1:01         ` 2.6.10-rc2-mm4 Chris Wright
2004-12-02  1:11           ` 2.6.10-rc2-mm4 Jeff Mahoney
2004-12-02 13:32           ` 2.6.10-rc2-mm4 Stephen Smalley
2004-12-02 13:15         ` 2.6.10-rc2-mm4 Stephen Smalley
2004-12-07 19:57           ` 2.6.10-rc2-mm4 Jeff Mahoney
2004-12-07 20:28             ` 2.6.10-rc2-mm4 Stephen Smalley
2004-12-07 22:46               ` 2.6.10-rc2-mm4 Jeff Mahoney
2004-12-08 13:28                 ` 2.6.10-rc2-mm4 Stephen Smalley
2004-12-01  1:37 ` 2.6.10-rc2-mm4 Matthew Dobson
2004-12-03  9:23   ` 2.6.10-rc2-mm4 Andi Kleen
2004-12-01 21:10 ` 2.6.10-rc2-mm4 Adrian Bunk
2004-12-01 22:26   ` 2.6.10-rc2-mm4 Bill Davidsen
2004-12-02  0:18   ` 2.6.10-rc2-mm4 Bjorn Helgaas
2004-12-09 11:07 ` 2.6.10-rc2-mm4 William Lee Irwin III

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=20041203215927.GE1709@hygelac \
    --to=tripperda@nvidia.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 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.