public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Inefficient ia64 system call implementation in glibc
Date: Mon, 22 Sep 2003 21:25:36 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106426598631350@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106398916511816@msgid-missing>

>>>>> On Sat, 20 Sep 2003 15:01:26 +0200, Andreas Schwab <schwab@suse.de> said:

  Andreas> "Jim Hull" <jim.hull@hp.com> writes:
  >> But my real issue with the performance of this code is not with
  >> sign-extend or the scheduling these instructions, it's with the
  >> break instruction.  I may be mistaken, but hasn't it been many
  >> months since David Mosberger implemented all the kernel
  >> infrastructure needed to support syscalls using the epc
  >> instruction?

  Andreas> It's only implemented in 2.6 so far.

No, the glibc support is completely orthogonal to the kernel support.
If glibc uses the new stubs on a kernel which doesn't support
kernel-entry via EPC, it will transparently fall back to using BREAK.

	--david

  parent reply	other threads:[~2003-09-22 21:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 16:32 Inefficient ia64 system call implementation in glibc H. J. Lu
2003-09-19 17:29 ` Grant Grundler
2003-09-19 21:46 ` John Worley
2003-09-19 23:32 ` Jim Hull
2003-09-20 13:01 ` Andreas Schwab
2003-09-21 21:04 ` Richard Henderson
2003-09-22 19:39 ` H. J. Lu
2003-09-22 21:25 ` David Mosberger [this message]
2003-09-22 23:21 ` Richard Henderson

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-106426598631350@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