From: Nauman Tahir <nauman.tahir@gmail.com>
To: Andi Kleen <ak@suse.de>
Cc: kernelnewbies@nl.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: X86_64 and X86_32 bit performance difference [Revisited]
Date: Tue, 10 Jan 2006 02:50:12 -0800 [thread overview]
Message-ID: <f0309ff0601100250p55bc635aw98fcd55b327e2392@mail.gmail.com> (raw)
In-Reply-To: <p734q4dxnnb.fsf@verdi.suse.de>
On 09 Jan 2006 19:27:20 +0100, Andi Kleen <ak@suse.de> wrote:
> Nauman Tahir <nauman.tahir@gmail.com> writes:
>
> > I have posted this problem before. Now mailing again after testing as
> > recommeded in previous replys.
> > My configuration is:
>
> Most likely it's related to you misusing the PCI DMA API in some way.
> Review Documentation/DMA-mapping.txt closely.
>
> If that doesn't turn on the light try oprofile.
what is oprofile???
>
> -Andi
>
prev parent reply other threads:[~2006-01-10 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 6:29 X86_64 and X86_32 bit performance difference [Revisited] Nauman Tahir
2006-01-09 7:51 ` Arjan van de Ven
2006-01-10 10:49 ` Nauman Tahir
2006-01-10 10:53 ` Nauman Tahir
2006-01-10 21:14 ` Arjan van de Ven
2006-01-09 18:27 ` Andi Kleen
2006-01-10 10:50 ` Nauman Tahir [this message]
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=f0309ff0601100250p55bc635aw98fcd55b327e2392@mail.gmail.com \
--to=nauman.tahir@gmail.com \
--cc=ak@suse.de \
--cc=kernelnewbies@nl.kernel.org \
--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