linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Kotler <fbkotler@zytor.com>
To: £ukasz <blurrpp@yahoo.com>
Cc: linux-assembly@vger.kernel.org
Subject: Re: Appendix: multithreating HOWTO ? :)
Date: Sun, 23 Aug 2009 15:18:48 -0400	[thread overview]
Message-ID: <4A919618.5020107@zytor.com> (raw)
In-Reply-To: <203349.81852.qm@web50309.mail.re2.yahoo.com>

£ukasz wrote:
> thanks for answer, im experiment with system clone ( actualy fork i found in many manuals ) but i dont understand Frakns last sentence
> "Well, they *told* us not to do it that way. :)", to program multiproceses with fork ? Any way is there any way to make share memory for proceses ?

Just a "joke". I meant, using the int 80h (or syscall) interface. We're 
"supposed" to use the C interface.

Like Claudio, I'm a "32-bit guy" - and I don't know how to do 
multithreading even on 32-bit. But I think if you're going to use 64-bit 
registers, you'll have to use 64-bit sys_call numbers, put the 
parameters in regs compatible with the 64-bit ABI, and use "syscall" 
instead of "int 0x80". I don't think what you're doing will work, but 
I'm not equipped to try it.

You can share memory between processes by memmapping a region and 
flagging it MAP_SHARED (sys_fork or even separate executables). I 
*think* for threads, you'd want sys_clone, and all memory would be 
shared(?). I think your issue is going to be keeping your threads from 
read/writing the same memory at the same time. I'm a "single CPU guy", 
too, but I think multi-CPU is going to be "even worse".

I made an example using pthread_create - not that I want to use it 
either, but to see what it does for us. Easier to read the source, I'm 
sure, but no, I ran it in strace. Doing a bunch of "signal related" 
stuff I don't understand. I'm afraid I'm going to have to learn more 
about "signals" before I can proceed with this...

For those of us who need to learn about 64-bit programming, there's a 
tutorial:

<http://www.vikaskumar.org/wiki/index.php?title=X86-64_Tutorial>

Came across this, that looked interesting, too:

<http://milw0rm.org/papers/110>

Best,
Frank




--
To unsubscribe from this list: send the line "unsubscribe linux-assembly" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-08-23 19:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-22 16:48 multithreating HOWTO ? :) £ukasz
2009-08-23 10:29 ` Appendix: " £ukasz
2009-08-23 13:35   ` Claudio Fontana
2009-08-23 15:04     ` Frank Kotler
2009-08-23 15:23       ` Claudio Fontana
2009-08-23 16:17         ` £ukasz
2009-08-23 19:18           ` Frank Kotler [this message]
2009-08-23 21:02           ` linuxasm
2009-08-23 19:13         ` £ukasz

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=4A919618.5020107@zytor.com \
    --to=fbkotler@zytor.com \
    --cc=blurrpp@yahoo.com \
    --cc=linux-assembly@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;
as well as URLs for NNTP newsgroup(s).