From: Nauman Tahir <nauman.tahir@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernelnewbies@nl.kernel.org
Subject: Re: X86_64 and X86_32 bit performance difference [Revisited]
Date: Tue, 10 Jan 2006 02:49:34 -0800 [thread overview]
Message-ID: <f0309ff0601100249y4ffa3596sa2a623015cdca66b@mail.gmail.com> (raw)
In-Reply-To: <1136793080.2936.14.camel@laptopd505.fenrus.org>
On 1/9/06, Arjan van de Ven <arjan@infradead.org> wrote:
> On Sun, 2006-01-08 at 22:29 -0800, Nauman Tahir wrote:
> > Hello All
> > I have posted this problem before. Now mailing again after testing as
> > recommeded in previous replys.
> > My configuration is:
> >
> > Hardware:
> > HP Proliant DL145 (2 x AMD Optaron 144)
> > 14 GB RAM
> >
> > OS:
> > FC 4
> >
> > Kernel
> > 2.6.xx
>
> You *STILL* have not posted the URL to your source code.
> How is anyone supposed to help you without that?????
I have attached a file which I use as thread API. Complete code is
quiet large and also need proper description. which i would be posting
if needed.
I hope I make my problem clear: I repeat : same code is giving alot of
performance degradation on previously mentioned configuration. One
suspect is the thread library.
dts_thread_t *dts_register_thread(void (*run) (void *), const char
*name, void * private)
is the function to register my thread handler
void dts_wakeup_thread(dts_thread_t *thread)
is the function in the dts_thread.c which i use to run my thread.
all my thread handlers either
call generic_make_request some times for my RAMDISK and sometimes for
my Target device [SCSI DISK or local HDD partition]
OR
uses list.h
>
>
>
>
>
next prev parent reply other threads:[~2006-01-10 10:49 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 [this message]
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
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=f0309ff0601100249y4ffa3596sa2a623015cdca66b@mail.gmail.com \
--to=nauman.tahir@gmail.com \
--cc=arjan@infradead.org \
--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