From: Jason Borden <jborden@sorenson.com>
To: Lada 'Ray' Lostak <ray@unreal64.net>, linux-assembly@vger.kernel.org
Subject: Re: Threads, timing
Date: Mon, 7 Oct 2002 10:28:32 -0600 [thread overview]
Message-ID: <200210071028.32212.jborden@sorenson.com> (raw)
In-Reply-To: <002801c26dd0$22da4430$0d01a8c0@utopia>
I have to compliment you on your desire to make your own thread syncronization
functions, however, the linux kernel does support native system calls to do
this for you if you are interested. The kernel call is "ipc" which implements
Sys V interprocess communication, including semaphores. You can get more
information in the man pages, eg: man ipc, man semctl, man semget, man semop.
From what I gather, the sysv ipc functions aren't exactly as fast at thread
syncronization as a windows implementation, but that is being fixed in the
2.5.x kernels using the new futex kernel call.
Hope that helps,
Jason
On Monday 07 October 2002 01:07 am, Lada 'Ray' Lostak wrote:
> Hi there :o)
>
> I have small advanced problem about threads and sync. As you may
> remeber, we are porting huge application to linux. It is not problem at
> all, because we expect applications to be ported, so, it is ready. But
> right now, we don't know, if we can use more 'optimized' way for sync
> objects, because we don't know, if we can implement on linuxes. On linuxes,
> we don't use glibc at all, we use direct kernel calls (except sysdep
> components, such as database wrappers and other - they are compiled
> standalone). I don't want to flamewar about this (as usually :) bt it is
> done for shariong binaries acros more OS and one CPU.
>...
next prev parent reply other threads:[~2002-10-07 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 7:07 Threads, timing Lada 'Ray' Lostak
2002-10-07 16:28 ` Jason Borden [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-07 18:05 Lada 'Ray' Lostak
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=200210071028.32212.jborden@sorenson.com \
--to=jborden@sorenson.com \
--cc=linux-assembly@vger.kernel.org \
--cc=ray@unreal64.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.