From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: Confused about fsystemcalls
Date: Thu, 30 Jan 2003 00:23:46 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805775@msgid-missing> (raw)
>>>>> On Thu, 30 Jan 2003 11:07:51 +1100, Peter Chubb <peter@chubb.wattle.id.au> said:
Peter> The mygetpid() call appears to return the correct value.
Peter> Our figures show over an average of ten runs: --- glibc
Peter> getpid() takes 579 cycles, stddev 24 --- mygetpid takes 1468
Peter> cycles, stddev 286
Have you tried on a McKinley? The numbers you quote for the standard
getpid() look like for Merced. I never tried on Merced, though I
don't know of why it shouldn't work fast, off hand.
Peter> I was also a little confused about the entry put into the ELF
Peter> AUX vector -- was the value or the user-space address of
Peter> syscall_via_epc meant to go into the vector? Currently it
Peter> says in include/asm-ia64/elf.h
Oh, it was broken. I just fixed it today (since I got glibc to work
with the new syscall stub) and it's in the lia64 bk tree now.
--david
next reply other threads:[~2003-01-30 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 0:23 David Mosberger [this message]
2003-01-30 4:31 ` [Linux-ia64] Re: Confused about fsystemcalls Peter Chubb
2003-01-30 4:39 ` David Mosberger
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=marc-linux-ia64-105590709805775@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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