Re: Appendix: multithreating HOWTO ? :)

[£ukasz <blurrpp@xxxxxxxxx>]

more info for example.

http://stackoverflow.com/questions/807506/threads-vs-processes-in-linux

as u see with litle work i can create process (fork) from thread (clone), i have to make some changes in systme tables etc. now need to read little more kernel sys call source.

--- On Sun, 8/23/09, Claudio Fontana <claudio.fontana@xxxxxxxxx> wrote:

> From: Claudio Fontana <claudio.fontana@xxxxxxxxx>
> Subject: Re: Appendix: multithreating HOWTO ? :)
> To: "Frank Kotler" <fbkotler@xxxxxxxxx>
> Cc: "£ukasz" <blurrpp@xxxxxxxxx>, linux-assembly@xxxxxxxxxxxxxxx
> Date: Sunday, August 23, 2009, 5:23 PM
> On Sun, Aug 23, 2009 at 5:04 PM,
> Frank Kotler<fbkotler@xxxxxxxxx>
> 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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html