mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4.4 alpha semaphores optimization
Date: Fri, 4 May 2001 13:54:01 +0400	[thread overview]
Message-ID: <20010504135401.A2346@jurassic.park.msu.ru> (raw)
In-Reply-To: <20010503194747.A552@jurassic.park.msu.ru> <14842.988968173@warthog.cambridge.redhat.com>
In-Reply-To: <14842.988968173@warthog.cambridge.redhat.com>; from dhowells@redhat.com on Fri, May 04, 2001 at 10:22:53AM +0100

On Fri, May 04, 2001 at 10:22:53AM +0100, David Howells wrote:
> Hello Ivan,

Hello David!

> I don't know whether it will (a) compile, or (b) work... I don't have an alpha
> to play with.

It looks ok at a first glance, I can try it today.

> I also don't know the alpha function calling convention, so I can't put direct
> calls to the fallback routines in lib/rwsem.c from the ".subsection 2"
> bits. Can you do that, or can you tell me how the calling convention works?

Calling C routines from inline asm is quite painful on alpha. Lots of
registers will be clobbered, so you need some wrapper functions preserving
them. It was done in 2.2 this way, but that code was hardly maintainable...

Ivan.

  reply	other threads:[~2001-05-04  9:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-03 15:47 Ivan Kokshaysky
2001-05-03 17:28 ` Andrea Arcangeli
2001-05-04  9:15   ` Ivan Kokshaysky
2001-05-04 14:33     ` Andrea Arcangeli
2001-05-04 17:02       ` Ivan Kokshaysky
2001-05-04 17:16         ` Andrea Arcangeli
2001-05-04  9:22 ` David Howells
2001-05-04  9:54   ` Ivan Kokshaysky [this message]
2001-05-04 16:46   ` Ivan Kokshaysky
2001-05-04 21:12 ` Richard Henderson
2001-05-05 13:55   ` Ivan Kokshaysky
2001-05-06  6:55     ` Ivan Kokshaysky
2001-05-04 21:13 ` Richard Henderson
2001-05-05 14:17   ` Ivan Kokshaysky
2001-05-05 17:06     ` __builtin_expect vs inlining 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=20010504135401.A2346@jurassic.park.msu.ru \
    --to=ink@jurassic.park.msu.ru \
    --cc=dhowells@redhat.com \
    --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

all inboxes | Powered by JetHome®