Browsing this Thread:
1 Anonymous Users
|
Re: Questions abt AROS SMP
|
||||
|---|---|---|---|---|
|
Home away from home
 
|
all right! Thank you Kalamatee for explaining!
(It is alway hard for me to get my head around all that concurrent stuff...)
Posted on: 2018/6/11 20:09
|
|||
|
||||
|
Re: Questions abt AROS SMP
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
Of course, that's why the _port_ has locking - only one will get to use it at a time ;) And to clarify - it is irrelevant to anything but platforms where "smp" is possible. For now this is only the x86 branches, but also ARM will work the same way eventually.
Posted on: 2018/6/11 19:55
|
|||
|
||||
|
||||
|
Re: Questions abt AROS SMP
|
||||
|---|---|---|---|---|
|
Home away from home
|
That sounds smart!
 (but if tasks are not locked two or more tasks could try a port exactly at the same time, couldn't they?)
Posted on: 2018/6/11 19:54
|
|||
|
||||
|
Re: Questions abt AROS SMP
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
On smp capable systems (not necessarily enabled) the message port has an embedded lock structure, that is used by exec to arbitrate access to the port. Only access to the "port" is locked, not all tasks/cores ;) On normal (non smp) builds of e.g. i386 (which is smp capable) these fields are present but unused, its only on an actual smp build they are utilised. It does mean if you use an embedded port structure, it _must_ be cleared before use (or the locking mechanism may think a lock is already held on the port). Quote:
Posted on: 2018/6/11 19:42
|
|||
|
|
||||
|
||||
|
Re: Questions abt AROS SMP
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
Execs messaging and signaling is based on a single core concept ... so I see some complications here ... so basically Exec need to lock all tasks/cores if you send a message? Quote:
Thanks! I will have a look at these.
Posted on: 2018/6/11 19:18
|
|||
|
||||
|
Re: Questions abt AROS SMP
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
Im not sure what your mean exactly - but for now it should be only used to offload work to support "threads" running in a separate task, and messaging results/data between them. Its still incomplete (and will be for some time, due to my circumstances, unless someone else wants to contribute), so for the time being, its not particularly safe to access anything other than data your application shares between the threads. Quote:
Tasks are assigned to whichever CPU's/core's they have a suitable affinity mask for, so a task which has all the bits in the mask set to 1 will get scheduled on any CPU/core available, otherwise it will only run on the CPUs/cores it has requested. IPC is handled by messaging/signalling the other tasks running on other CPUS/cores. There are 2 examples/demos under Developer/Debug/Tests/smp that show this in use, using slightly different strategies to achieve it.
Posted on: 2018/6/11 18:59
|
|||
|
|
||||
|
||||
|
Re: Questions abt AROS SMP
|
||||
|---|---|---|---|---|
|
Home away from home
|
Since there is a question missing: I have one!
Is there any "best practice" on how to make good use of this new feature? E.g. assigning tasks to a certain CPU or best way of IPC? (I guess what we call inter-process on AROS would be considered inter-thread on other systems?)
Posted on: 2018/6/11 18:53
|
|||
|
||||
|
Re: Questions abt AROS SMP
|
||||
|---|---|---|---|---|
|
Home away from home
|
So, whats your question exactly?
Posted on: 2018/6/11 16:33
|
|||
|
|
||||
|
||||
|
Questions abt AROS SMP
|
||||
|---|---|---|---|---|
|
Just popping in
 
|
I tested latest AROS SMP Nightly on a Pentium IV 3.2 Ghz Hyper Threading PC and on the default Vesa boot Option the boot Process halts.. I tested the slow ata Option and had a successfull boot.. then I tested the 1280x1024 VESA Screen Resolution and AROS SMP managed also to boot into Wanderer successfully!
Sad the Soundcard (SB Live!) and Network Drivers (RTL 8169) still don't seem to work!
Posted on: 2018/6/11 6:36
|
|||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.
