public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <m.monnerie@zmi.at>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andi Kleen <ak@suse.de>, Allen Martin <AMartin@nvidia.com>,
	Chris Wedgwood <cw@f00f.org>,
	linux-kernel@vger.kernel.org
Subject: Re: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
Date: Sat, 4 Mar 2006 07:34:41 +0100	[thread overview]
Message-ID: <200603040734.46091@zmi.at> (raw)
In-Reply-To: <4408C1E1.7090006@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

On Freitag, 3. März 2006 23:23 Jeff Garzik wrote:
> I'll happen but not soon.  Motivation is low at NV and here as well,
> since newer NV is AHCI.  The code in question, "NV ADMA", is
> essentially legacy at this point -- though I certainly acknowledge
> the large current installed base.  Just being honest about the
> current state of things...

I'd like to raise motivation a lot because most MB sold here (central 
Europe) are Nforce4 with Athlon64x2 at the moment. It would be nice 
from vendors if they support OSS developers more, as it's their 
interest to have good drivers.

For the moment, I'd recommend *against* using Nforce4 because of that 
problems we had (and that caused us a lot of unpaid repairing work). 
Hopefully NV does something quick to resolve the remaining issues, 
especially as the 4GB "border" is hit more and more often.

mfg zmi
-- 
// Michael Monnerie, Ing.BSc  ---   it-management Michael Monnerie
// http://zmi.at           Tel: 0660/4156531          Linux 2.6.11
// PGP Key:   "lynx -source http://zmi.at/zmi2.asc | gpg --import"
// Fingerprint: EB93 ED8A 1DCD BB6C F952  F7F4 3911 B933 7054 5879
// Keyserver: www.keyserver.net                 Key-ID: 0x70545879

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-03-04  6:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-03 21:27 PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution Allen Martin
2006-03-03 22:12 ` Andi Kleen
2006-03-03 22:23   ` Jeff Garzik
2006-03-03 22:32     ` Andi Kleen
2006-03-04  6:34     ` Michael Monnerie [this message]
     [not found] <5Mq18-1Na-21@gated-at.bofh.it>
     [not found] ` <5MqNc-2Y5-3@gated-at.bofh.it>
     [not found]   ` <5MqX4-39H-21@gated-at.bofh.it>
     [not found]     ` <5MyAS-5zh-5@gated-at.bofh.it>
2006-03-07  0:15       ` Robert Hancock
2006-04-02  7:51         ` Joerg Bashir
2006-04-02  8:00           ` Muli Ben-Yehuda
2006-04-02  8:24             ` Joerg Bashir
2006-04-02 11:16           ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2006-03-01 23:23 Michael Monnerie
2006-03-02  1:03 ` Andi Kleen
2006-03-02  9:59   ` Jens Axboe
2006-03-03  8:16   ` Chris Wedgwood
2006-03-03 11:00     ` Andi Kleen
     [not found] ` <200603021316.38077.ak@suse.de>
     [not found]   ` <4406E226.4050806@pobox.com>
2006-03-02 12:26     ` Andi Kleen
2006-03-02 12:31       ` Jens Axboe
2006-03-02 12:33       ` Jeff Garzik
     [not found]   ` <20060302123033.GL4329@suse.de>
2006-03-02 13:09     ` Andi Kleen
2006-03-02 13:10       ` Jens Axboe
2006-03-02 13:33         ` Andi Kleen
2006-03-02 13:33           ` Jens Axboe
2006-03-02 13:46             ` Andi Kleen
2006-03-02 13:49               ` Jens Axboe
2006-03-02 13:58                 ` Andi Kleen
2006-03-02 14:14                   ` Jens Axboe
2006-03-02 14:35                     ` Andi Kleen
2006-03-02 14:38                       ` Jens Axboe

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=200603040734.46091@zmi.at \
    --to=m.monnerie@zmi.at \
    --cc=AMartin@nvidia.com \
    --cc=ak@suse.de \
    --cc=cw@f00f.org \
    --cc=jgarzik@pobox.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