From: "Leonid Grossman" <leonid.grossman@s2io.com>
To: "'Linux Kernel'" <linux-kernel@vger.kernel.org>
Cc: "'ravinandan arakali'" <ravinandan.arakali@s2io.com>
Subject: pci_alloc_consistent()
Date: Thu, 22 Jan 2004 17:59:47 -0800 [thread overview]
Message-ID: <000101c3e154$949dd520$7310100a@S2IOtech.com> (raw)
In-Reply-To: <20040122234803.GC18316@widomaker.com>
Are there any known issues with pci_alloc_consistent() allocating more
than 1MB?
One of our developers seems to recall a thread but we can't find it...
We are using pci_alloc_consistent() in our 10GbE driver, to allocate
memory for DMA transfers between
host and device.
If we allocate under 1MB, everything works fine. When the allocation is
more than 1 MB, allocation call does not return any failure but some
data corruption seems to take place beyond the 1 MB space.
Is this a known problem? The system is 2-way Itanium, running 2.4.21
kernel.
Thanks in advance, Leonid
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of
> Charles Shannon Hendrix
> Sent: Thursday, January 22, 2004 3:48 PM
> To: Linux Kernel
> Subject: Re: Nvidia drivers and 2.6.x kernel
>
>
> Thu, 22 Jan 2004 @ 12:12 +0000, Kieran said:
>
> > How strange. I run slack 9.1 and 2.6.1, just grabbed the 4496
> > pre-patched file from http://www.sh.nu/download/nvidia/ and
> installed it
> > as I would on 2.4. Works a charm.
>
> How's the performance?
>
> I have found the 4496 and 5328 drivers lowered my performance.
>
> 5328 is supposed to be faster mip-mapping and faster when
> running with vertical blank sync, but I didn't see it myself.
> It also caused quite a few sound artifacts from my Live! sound card.
>
> Anyone done a driver-by-driver benchmark?
>
> I got tired of it, but here's the performance order on my
> system from fastest to slowest:
>
> 4620
> 3xxx (last stable 3xxx driver)
> 4496
> 5328
>
> Mostly what I look for are not benchmark numbers, but notable
> hesitation in programs and interactive response, and side
> effects like bad sound artifacts.
>
>
>
>
> --
> UNIX/Perl/C/Pizza____________________s h a n n o n@wido !SPAM
> maker.com
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to
> majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-01-23 2:00 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 ` Leonid Grossman [this message]
2004-01-23 8:50 ` pci_alloc_consistent() Jes Sorensen
2004-01-23 14:37 ` pci_alloc_consistent() Leonid Grossman
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='000101c3e154$949dd520$7310100a@S2IOtech.com' \
--to=leonid.grossman@s2io.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox