linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Kotler <fbkotler@zytor.com>
To: Claudio Fontana <claudio.fontana@gmail.com>
Cc: £ukasz <blurrpp@yahoo.com>, linux-assembly@vger.kernel.org
Subject: Re: Appendix: multithreating HOWTO ? :)
Date: Sun, 23 Aug 2009 11:04:46 -0400	[thread overview]
Message-ID: <4A915A8E.4000207@zytor.com> (raw)
In-Reply-To: <4A9145B0.50507@gmail.com>

Claudio Fontana wrote:
> £ukasz wrote:
>> in appendix i want to just precize problem. Broblem is how to write, 
>> create etc, shared memory for parent and child proceses, where they 
>> could for example exchange wariables
> 
> You are using fork. Fork is used to create new processes.
> You probably want clone instead, to create new threads and specify
> which resources to share between the two threads.
> 
> man 2 clone
> 
> sys_clone is 120 (0x78).

Is that a 64-bit sys_call number? I thought they'd changed that on us. 
AFAIK, __NR_clone is 56 these days... and "syscall" replaces int 0x80. A 
real "curve ball" to asm programmers! Well, they *told* us not to do it 
that way. :)

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 15:04 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 [this message]
2009-08-23 15:23       ` Claudio Fontana
2009-08-23 16:17         ` £ukasz
2009-08-23 19:18           ` Frank Kotler
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=4A915A8E.4000207@zytor.com \
    --to=fbkotler@zytor.com \
    --cc=blurrpp@yahoo.com \
    --cc=claudio.fontana@gmail.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).