All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Leonid Grossman" <leonid.grossman@s2io.com>
To: "'Jes Sorensen'" <jes@wildopensource.com>
Cc: "'Linux Kernel'" <linux-kernel@vger.kernel.org>,
	"'ravinandan arakali'" <ravinandan.arakali@s2io.com>
Subject: RE: pci_alloc_consistent()
Date: Fri, 23 Jan 2004 06:37:47 -0800	[thread overview]
Message-ID: <000001c3e1be$79904640$0400a8c0@S2IOtech.com> (raw)
In-Reply-To: <yq07jzj2gmx.fsf@wildopensource.com>

Hi Jes,

> Leonid,
> 
> What type of Itanium box? It's possible what you're seeing is 
> caused by a bug in the IOMMU code, but we would need to know 
> which one (HP, SGI or someone else's).

The problem with pci_alloc_consistent()above 1MB happens on HP rx2600
(this is 2U dual-Itanium 900MHz pci-x 133 box). I don't believe it
happens on 64 bit Opterons. Today we are going to test Dell and SGI
Itanium systems, as well as a bit newer rx 2600 with Itanium-2 1.5GHz -
I'll let you know by the end of the day.

Thanks, Leonid


> 
> Cheers,
> Jes
> 


  reply	other threads:[~2004-01-23 14:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 23:04 Nvidia drivers and 2.6.x kernel Christian Unger
     [not found] ` <400FB4AA.8000109@yahoo.com.br>
2004-01-22 11:52   ` Christian Unger
2004-01-22 12:12     ` Kieran
2004-01-22 22:42       ` Christian Unger
     [not found]         ` <401052C6.7040500@ihateaol.co.uk>
2004-01-25 23:24           ` Christian Unger
2004-01-27 22:49             ` Charles Shannon Hendrix
2004-01-31  3:41               ` nVidia driver uses far less memory now, was " Charles Shannon Hendrix
2004-01-22 23:48       ` Charles Shannon Hendrix
2004-01-23  1:59         ` pci_alloc_consistent() Leonid Grossman
2004-01-23  8:50           ` pci_alloc_consistent() Jes Sorensen
2004-01-23 14:37             ` Leonid Grossman [this message]
2004-01-23 18:11               ` pci_alloc_consistent() Alex Williamson
2004-01-22 23:40     ` Nvidia drivers and 2.6.x kernel Charles Shannon Hendrix

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='000001c3e1be$79904640$0400a8c0@S2IOtech.com' \
    --to=leonid.grossman@s2io.com \
    --cc=jes@wildopensource.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ravinandan.arakali@s2io.com \
    /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.