Re: Appendix: multithreating HOWTO ? :)

£ukasz <[email protected]> Sun, 23 Aug 2009 09:17:59 -0700 (PDT)
Newsgroups org.kernel.vger.linux-assembly
Message-ID <[email protected]>
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 ?

Lukas

--- On Sun, 8/23/09, Claudio Fontana <[email protected]> wrote:

> From: Claudio Fontana <[email protected]>
> Subject: Re: Appendix: multithreating HOWTO ? :)
> To: "Frank Kotler" <[email protected]>
> Cc: "£ukasz" <[email protected]>, [email protected]
> Date: Sunday, August 23, 2009, 5:23 PM
> On Sun, Aug 23, 2009 at 5:04 PM,
> Frank Kotler<[email protected]>
> wrote:
> > 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
> 
> I am still on good old 32bit. On 64 bit system call numbers
> are indeed
> completely different.
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-assembly" in
> the body of a message to [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


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