- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Atomic commits

by stepharo

I agree (see my mails about sending diffs to the mailing-lists.) People do not listen to me so ... Le 6/1/16 19:13, Nicolas Cellier a Ã©crit : > Hi, > I wish the commits were much more atomic than they currently are... > With current practice, reviewing the changes is near to impossible: > - it requires far too much concentration > - it's just impossible through github web interface > > For example, I did wander if the structure fields were correclty > aligned in: > https://github.com/pharo-project/pharo-core/blame/5986a695fb28834247a90dbf8… > because I see no code for aligning the offsets... > > But I cannot even navigate in the history... If I do so, > https://github.com/pharo-project/pharo-core/commit/dfd4f3ae0f0b0af7766c1405… > > the page tells me > "Sorry, we could not display the entire diff because too many files > (2,121) changed" > and I couldn't find a way of displaying the portion of interest. > > I thus loose the ability to deposit a comment. > > I can still open a fresh Pharo image and browse and review the whole > code snapshot there. > Or I can navigate more easily in history with git tools. > But if I wanted a lightweight review thru web, focusing on the diffs > and navigating a bit in history without replicating the repository, I > can't. > > While ranting, it's nice to have the commits performed by a jenkins > server, but how do we track the authors of original modifications? > In a normal git based development, there would be feature branches > integrated/merged in trunk/master by whatever process. > But in current process i fail to capture such information... > > This gives a taste of under-powered use of the tools, and I wander if > being visible in these conditions is a good thing: we don't expose the > best practices.

Jan. 7, 2016

Re: [Pharo-dev] [ANN] I created a web page so you can stalk me :)

by stepharo

This is not to be visible. This is to educate you guys :) The point is how much time does it take esteban to fix FFI How much worth is that? All these questions and like that you know what esteban is doing for real when you put money in the consortium. Stef Le 7/1/16 18:48, Esteban A. Maringolo a Ã©crit : > Nice! > > However I wouldn't say you're not visible in the community. ;-) > > Esteban A. Maringolo > > > 2016-01-07 14:21 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> On 07 Jan 2016, at 18:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> Hi, >> >> Stef told me I need to make a bit more visibility my work, and while being >> in Togo I sketched an application I tested last few days and seems to be >> working fina. >> Of course, easiest way would be to use twitter as a work log, but I was not >> satisfied with the idea. Why? wellâ¦ some reasons are explained in the source >> page: >> >> - You can add formatting using pillar >> - You do not have 140 characters max (probably you will not need much more, >> but anyway, the limitation is annoying :P) >> - You can disqus (http://disqus.com) posts. >> - Posts are interpreted and links are detected and listed (so is easy to >> find them) >> - Since is made for my own work, it understand links like *case:12345* as a >> link to pharo fogbugz case 12345. >> - It has a command line! >> >> but another reason was because I wanted to try it (and I was bored in Togo >> waiting for the planes) >> I donât know how this experiment will work, but letâs give it a try :) >> >> http://log.smallworks.eu >> http://log.smallworks.eu/rss (you can suscribe with your reader, so you do >> not need to go to the page) >> https://github.com/estebanlm/worklog >> >> Enjoy stalking me :) >> >> Esteban >> >> >> btw is very possible that you took it downâ¦ I never tested with other than >> my self. >> â¦ this is running in Pharo 5 with spur (I wanted to test stability too) :P >> >> Esteban >> >

Jan. 7, 2016

Changing performance balance between CPU & non-volatile storage

by Ben Coman

An enlightening article (if a bit long). I wonder how non-volatile storage being faster than a CPU might affect Pharo systems. Perhaps the importance of migrating between live and backup Images gains in importance to backups via files. https://queue.acm.org/detail.cfm?id=2874238 cheers -ben

Jan. 7, 2016

Re: [Pharo-dev] [Vm-dev] Where to get Monitor implementation based on primitives?

by Eliot Miranda

Hi Ben, On Thu, Jan 7, 2016 at 10:39 AM, Ben Coman <btc(a)openinworld.com> wrote: > > On Fri, Jan 8, 2016 at 1:20 AM, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > > > > and here's a version with a better class comment > > > > On Thu, Jan 7, 2016 at 9:12 AM, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > >> > >> Hi Denis, Hi ClÃ©ment, Hi Frank, > >> > >> On Thu, Jan 7, 2016 at 5:34 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> > wrote: > >>> > >>> Hello, > >>> > >>> Eliot, please, you told me you had the code and Denis is interested. > >>> > >>> It uses 3 primitives for performance. > >> > >> > >> Forgive the delay. I thought it proper to ask permission since the > code was written while I was at Qwaq. I'm attaching the code in a fairly > raw state, see the attached. The code is MIT, but copyright 3DICC. > >> > >> It is a plugin replacement for Squeak's Mutex, and with a little > ingenuity could be a replacement for Squeak's Monitor. It is quicker > because it uses three new primitives to manage entering a critical section > and setting the owner, exiting the critical section and releasing the > owner, and testing if a critical section, entering if the section is > unowned. The use of the primitives means fewer block activations and > ensure: blocks in entering and exiting the critical section, and that's the > actual cause of the speed-up. > >> > >> You can benchmark the code as is. Here are some results on 32-bit > Spur, on my 2.2GHz Core i7 > >> > >> {Mutex new. Monitor new. CriticalSection new} collect: > >> [:cs| | n | > >> n := 0. > >> [cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n > := n + 1]. cs critical: [n := n + 1]. cs critical: [n := n + 1]. > >> cs critical: [n := n - 1]. cs critical: [n := n - 1]. cs critical: [n > := n - 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. > >> n ] bench] > >> > >> {Mutex new. Monitor new. CriticalSection new} collect: > >> [:cs| | n | > >> n := 0. > >> cs class name, ' -> ', > >> [cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n > := n + 1]. cs critical: [n := n + 1]. cs critical: [n := n + 1]. > >> cs critical: [n := n - 1]. cs critical: [n := n - 1]. cs critical: [n > := n - 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. > >> n ] bench] > >> > >> #( 'Mutex -> 440,000 per second. 2.27 microseconds per run.' > >> 'Monitor -> 688,000 per second. 1.45 microseconds per run.' > >> 'CriticalSection -> 1,110,000 per second. 900 nanoseconds per run.') > >> > > This is great Eliot. Thank you and 3DICC. After loading the changeset > into Pharo-50515 (32 bit Spur) I get the following results on my > laptop i5-2520M @ 2.50GHz > > #('Mutex -> 254,047 per second' > 'Monitor -> 450,442 per second' > 'CriticalSection -> 683,393 per second') > > In a fresh Image "Mutex allInstances basicInspect" lists just two > mutexes... > 1. NetNameResolver-->ResolverMutex > 2. ThreadSafeTranscript-->accessSemaphore > I hate myself for getting distracted but I'm finding this is un. One can migrate to the new representation using normal Monticello loads by In the first version redefine Mutex and Monitor to subclass LinkedList and have their owner/ownerProcess inst var first (actually third after firstLink & lastLink), and add the primitives. In the next version check that all Mutex and Monitor instanes are unowned and then redefine to discard excess inst vars Let me test this before committing, and see that all tests are ok. > cheers -ben > > >> Replacement is probably trivial; rename Mutex to OldMutex, rename > CriticalSection to Mutex, recompile. But there are lots of mutexes in the > system and these are potentially owned. Transforming unowned ones is > trivial, but transforming owned ones is, I think, impossible. But at least > in my system there are no owned mutexes or monitors. > >> > >> Frank (or anyone else), would you be interested in creating a > replacement for Squeak's Monitor based on CriticalSection? > >> > >> > >> Here are the two business methods: > >> CriticalSection methods for mutual exclusion > >> critical: aBlock > >> "Evaluate aBlock protected by the receiver." > >> ^self primitiveEnterCriticalSection > >> ifTrue: [aBlock value] > >> ifFalse: [aBlock ensure: [self primitiveExitCriticalSection]] > >> > >> critical: aBlock ifLocked: lockedBlock > >> "Answer the evaluation of aBlock protected by the receiver. If it is > already in a critical > >> section on behalf of some other process answer the evaluation of > lockedBlock." > >> ^self primitiveTestAndSetOwnershipOfCriticalSection > >> ifNil: [lockedBlock value] > >> ifNotNil:[:alreadyOwner| > >> alreadyOwner > >> ifTrue: [aBlock value] > >> ifFalse: [aBlock ensure: [self primitiveExitCriticalSection]]] > >> > >> and the primitives: > >> CriticalSection methods for private-primitives > >> primitiveEnterCriticalSection > >> "Primitive. The receiver must be unowned or owned by the current > process to proceed. > >> Answer if the process is owned by the current process." > >> <primitive: 186> > >> self primitiveFailed > >> "In the spirit of the following" > >> "[owner ifNil: > >> [owner := Processor activeProcess. > >> ^false]. > >> owner = Processor activeProcess ifTrue: > >> [^true]. > >> self addLast: Processor activeProcess. > >> Processor activeProcess suspend] valueUnpreemptively" > >> > >> primitiveExitCriticalSection > >> "Primitive. Set te receiver to unowned and if any processes are waiting > on > >> the receiver then proceed the first one, indicating that the receiver > is unowned." > >> <primitive: 185> > >> self primitiveFailed > >> "In the spirit of the following" > >> "[owner := nil. > >> self isEmpty ifFalse: > >> [process := self removeFirst. > >> process resume]] valueUnpreemptively" > >> > >> primitiveTestAndSetOwnershipOfCriticalSection > >> "Primitive. Attempt to set the ownership of the receiver. > >> If the receiver is unowned set its owningProcess to the > >> activeProcess and answer false. If the receiver is owned > >> by the activeProcess answer true. If the receiver is owned > >> by some other process answer nil." > >> <primitive: 187> > >> self primitiveFail > >> "In the spirit of the following" > >> "[owner ifNil: > >> [owningProcess := Processor activeProcess. > >> ^false]. > >> owner = Processor activeProcess ifTrue: [^true]. > >> ^nil] valueUnpreemptively" > >> > >>> 2016-01-07 13:24 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >>>> > >>>> > >>>> Hello. > >>>> > >>>> I hear about new Monitor implementation based on new primitives. > >>>> Where to get it? > >> > >> > >> _,,,^..^,,,_ > >> best, Eliot > > > > > > > > > > -- > > _,,,^..^,,,_ > > best, Eliot > > > -- _,,,^..^,,,_ best, Eliot

Jan. 7, 2016

Re: [Pharo-dev] [ANN] I created a web page so you can stalk me :)

by Dimitris Chloupis

first to comment, aha !!! :D On Thu, Jan 7, 2016 at 7:50 PM Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Nice! > > However I wouldn't say you're not visible in the community. ;-) > > Esteban A. Maringolo > > > 2016-01-07 14:21 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > > > On 07 Jan 2016, at 18:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > Hi, > > > > Stef told me I need to make a bit more visibility my work, and while > being > > in Togo I sketched an application I tested last few days and seems to be > > working fina. > > Of course, easiest way would be to use twitter as a work log, but I was > not > > satisfied with the idea. Why? wellâ¦ some reasons are explained in the > source > > page: > > > > - You can add formatting using pillar > > - You do not have 140 characters max (probably you will not need much > more, > > but anyway, the limitation is annoying :P) > > - You can disqus (http://disqus.com) posts. > > - Posts are interpreted and links are detected and listed (so is easy to > > find them) > > - Since is made for my own work, it understand links like *case:12345* > as a > > link to pharo fogbugz case 12345. > > - It has a command line! > > > > but another reason was because I wanted to try it (and I was bored in > Togo > > waiting for the planes) > > I donât know how this experiment will work, but letâs give it a try :) > > > > http://log.smallworks.eu > > http://log.smallworks.eu/rss (you can suscribe with your reader, so you > do > > not need to go to the page) > > https://github.com/estebanlm/worklog > > > > Enjoy stalking me :) > > > > Esteban > > > > > > btw is very possible that you took it downâ¦ I never tested with other > than > > my self. > > â¦ this is running in Pharo 5 with spur (I wanted to test stability too) > :P > > > > Esteban > > > >

Jan. 7, 2016

Re: [Pharo-dev] [ANN] I created a web page so you can stalk me :)

by Esteban A. Maringolo

Nice! However I wouldn't say you're not visible in the community. ;-) Esteban A. Maringolo 2016-01-07 14:21 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 07 Jan 2016, at 18:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Stef told me I need to make a bit more visibility my work, and while being > in Togo I sketched an application I tested last few days and seems to be > working fina. > Of course, easiest way would be to use twitter as a work log, but I was not > satisfied with the idea. Why? wellâ¦ some reasons are explained in the source > page: > > - You can add formatting using pillar > - You do not have 140 characters max (probably you will not need much more, > but anyway, the limitation is annoying :P) > - You can disqus (http://disqus.com) posts. > - Posts are interpreted and links are detected and listed (so is easy to > find them) > - Since is made for my own work, it understand links like *case:12345* as a > link to pharo fogbugz case 12345. > - It has a command line! > > but another reason was because I wanted to try it (and I was bored in Togo > waiting for the planes) > I donât know how this experiment will work, but letâs give it a try :) > > http://log.smallworks.eu > http://log.smallworks.eu/rss (you can suscribe with your reader, so you do > not need to go to the page) > https://github.com/estebanlm/worklog > > Enjoy stalking me :) > > Esteban > > > btw is very possible that you took it downâ¦ I never tested with other than > my self. > â¦ this is running in Pharo 5 with spur (I wanted to test stability too) :P > > Esteban >

Jan. 7, 2016

Re: [Pharo-dev] [ANN] I created a web page so you can stalk me :)

by Esteban Lorenzano

> On 07 Jan 2016, at 18:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Stef told me I need to make a bit more visibility my work, and while being in Togo I sketched an application I tested last few days and seems to be working fina. > Of course, easiest way would be to use twitter as a work log, but I was not satisfied with the idea. Why? wellâ¦ some reasons are explained in the source page: > > - You can add formatting using pillar > - You do not have 140 characters max (probably you will not need much more, but anyway, the limitation is annoying :P) > - You can disqus (http://disqus.com <http://disqus.com/>) posts. > - Posts are interpreted and links are detected and listed (so is easy to find them) > - Since is made for my own work, it understand links like *case:12345* as a link to pharo fogbugz case 12345. > - It has a command line! > > but another reason was because I wanted to try it (and I was bored in Togo waiting for the planes) > I donât know how this experiment will work, but letâs give it a try :) > > http://log.smallworks.eu <http://log.smallworks.eu/> > http://log.smallworks.eu/rss <http://log.smallworks.eu/rss> (you can suscribe with your reader, so you do not need to go to the page) > https://github.com/estebanlm/worklog <https://github.com/estebanlm/worklog> > > Enjoy stalking me :) > > Esteban > btw is very possible that you took it downâ¦ I never tested with other than my self. â¦ this is running in Pharo 5 with spur (I wanted to test stability too) :P Esteban

Jan. 7, 2016

Re: [Pharo-dev] [Vm-dev] Where to get Monitor implementation based on primitives?

by Eliot Miranda

and here's a version with a better class comment On Thu, Jan 7, 2016 at 9:12 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Denis, Hi ClÃ©ment, Hi Frank, > > On Thu, Jan 7, 2016 at 5:34 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> > wrote: > >> Hello, >> >> Eliot, please, you told me you had the code and Denis is interested. >> >> It uses 3 primitives for performance. >> > > Forgive the delay. I thought it proper to ask permission since the code > was written while I was at Qwaq. I'm attaching the code in a fairly raw > state, see the attached. The code is MIT, but copyright 3DICC. > > It is a plugin replacement for Squeak's Mutex, and with a little ingenuity > could be a replacement for Squeak's Monitor. It is quicker because it uses > three new primitives to manage entering a critical section and setting the > owner, exiting the critical section and releasing the owner, and testing if > a critical section, entering if the section is unowned. The use of the > primitives means fewer block activations and ensure: blocks in entering and > exiting the critical section, and that's the actual cause of the speed-up. > > You can benchmark the code as is. Here are some results on 32-bit Spur, > on my 2.2GHz Core i7 > > {Mutex new. Monitor new. CriticalSection new} collect: > [:cs| | n | > n := 0. > [cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n := > n + 1]. cs critical: [n := n + 1]. cs critical: [n := n + 1]. > cs critical: [n := n - 1]. cs critical: [n := n - 1]. cs critical: [n := n > - 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. > n ] bench] > > {Mutex new. Monitor new. CriticalSection new} collect: > [:cs| | n | > n := 0. > cs class name, ' -> ', > [cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n := > n + 1]. cs critical: [n := n + 1]. cs critical: [n := n + 1]. > cs critical: [n := n - 1]. cs critical: [n := n - 1]. cs critical: [n := n > - 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. > n ] bench] > > #( 'Mutex -> 440,000 per second. 2.27 microseconds per run.' > 'Monitor -> 688,000 per second. 1.45 microseconds per run.' > 'CriticalSection -> 1,110,000 per second. 900 nanoseconds per run.') > > Replacement is probably trivial; rename Mutex to OldMutex, rename > CriticalSection to Mutex, recompile. But there are lots of mutexes in the > system and these are potentially owned. Transforming unowned ones is > trivial, but transforming owned ones is, I think, impossible. But at least > in my system there are no owned mutexes or monitors. > > Frank (or anyone else), would you be interested in creating a replacement > for Squeak's Monitor based on CriticalSection? > > > Here are the two business methods: > *CriticalSection methods for mutual exclusion* > *critical:* aBlock > "Evaluate aBlock protected by the receiver." > ^self primitiveEnterCriticalSection > ifTrue: [aBlock value] > ifFalse: [aBlock ensure: [self primitiveExitCriticalSection]] > > *critical:* aBlock *ifLocked:* lockedBlock > "*Answer the evaluation of aBlock protected by the receiver. If it is > already in a critical* > * section on behalf of some other process answer the evaluation of > lockedBlock.*" > ^self primitiveTestAndSetOwnershipOfCriticalSection > ifNil: [lockedBlock value] > ifNotNil:[:alreadyOwner| > alreadyOwner > ifTrue: [aBlock value] > ifFalse: [aBlock ensure: [self primitiveExitCriticalSection]]] > > and the primitives: > *CriticalSection methods for private-primitives* > *primitiveEnterCriticalSection* > "Primitive. The receiver must be unowned or owned by the current process > to proceed. > Answer if the process is owned by the current process." > <primitive: 186> > self primitiveFailed > "In the spirit of the following" > "[owner ifNil: > [owner := Processor activeProcess. > ^false]. > owner = Processor activeProcess ifTrue: > [^true]. > self addLast: Processor activeProcess. > Processor activeProcess suspend] valueUnpreemptively" > > *primitiveExitCriticalSection* > "Primitive. Set te receiver to unowned and if any processes are waiting on > the receiver then proceed the first one, indicating that the receiver is > unowned." > <primitive: 185> > self primitiveFailed > "In the spirit of the following" > "[owner := nil. > self isEmpty ifFalse: > [process := self removeFirst. > process resume]] valueUnpreemptively" > > *primitiveTestAndSetOwnershipOfCriticalSection* > "Primitive. Attempt to set the ownership of the receiver. > If the receiver is unowned set its owningProcess to the > activeProcess and answer false. If the receiver is owned > by the activeProcess answer true. If the receiver is owned > by some other process answer nil." > <primitive: 187> > self primitiveFail > "In the spirit of the following" > "[owner ifNil: > [owningProcess := Processor activeProcess. > ^false]. > owner = Processor activeProcess ifTrue: [^true]. > ^nil] valueUnpreemptively" > > 2016-01-07 13:24 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: >> >>> >>> Hello. >>> >>> I hear about new Monitor implementation based on new primitives. >>> Where to get it? >>> >> > _,,,^..^,,,_ > best, Eliot > -- _,,,^..^,,,_ best, Eliot

Jan. 7, 2016

[ANN] I created a web page so you can stalk me :)

by Esteban Lorenzano

Hi, Stef told me I need to make a bit more visibility my work, and while being in Togo I sketched an application I tested last few days and seems to be working fina. Of course, easiest way would be to use twitter as a work log, but I was not satisfied with the idea. Why? wellâ¦ some reasons are explained in the source page: - You can add formatting using pillar - You do not have 140 characters max (probably you will not need much more, but anyway, the limitation is annoying :P) - You can disqus (http://disqus.com) posts. - Posts are interpreted and links are detected and listed (so is easy to find them) - Since is made for my own work, it understand links like *case:12345* as a link to pharo fogbugz case 12345. - It has a command line! but another reason was because I wanted to try it (and I was bored in Togo waiting for the planes) I donât know how this experiment will work, but letâs give it a try :) http://log.smallworks.eu <http://log.smallworks.eu/> http://log.smallworks.eu/rss <http://log.smallworks.eu/rss> (you can suscribe with your reader, so you do not need to go to the page) https://github.com/estebanlm/worklog <https://github.com/estebanlm/worklog> Enjoy stalking me :) Esteban

Jan. 7, 2016

Re: [Pharo-dev] [Vm-dev] Where to get Monitor implementation based on primitives?

by Eliot Miranda

Hi Denis, Hi ClÃ©ment, Hi Frank, On Thu, Jan 7, 2016 at 5:34 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hello, > > Eliot, please, you told me you had the code and Denis is interested. > > It uses 3 primitives for performance. > Forgive the delay. I thought it proper to ask permission since the code was written while I was at Qwaq. I'm attaching the code in a fairly raw state, see the attached. The code is MIT, but copyright 3DICC. It is a plugin replacement for Squeak's Mutex, and with a little ingenuity could be a replacement for Squeak's Monitor. It is quicker because it uses three new primitives to manage entering a critical section and setting the owner, exiting the critical section and releasing the owner, and testing if a critical section, entering if the section is unowned. The use of the primitives means fewer block activations and ensure: blocks in entering and exiting the critical section, and that's the actual cause of the speed-up. You can benchmark the code as is. Here are some results on 32-bit Spur, on my 2.2GHz Core i7 {Mutex new. Monitor new. CriticalSection new} collect: [:cs| | n | n := 0. [cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. n ] bench] {Mutex new. Monitor new. CriticalSection new} collect: [:cs| | n | n := 0. cs class name, ' -> ', [cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n := n + 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. cs critical: [n := n - 1]. n ] bench] #( 'Mutex -> 440,000 per second. 2.27 microseconds per run.' 'Monitor -> 688,000 per second. 1.45 microseconds per run.' 'CriticalSection -> 1,110,000 per second. 900 nanoseconds per run.') Replacement is probably trivial; rename Mutex to OldMutex, rename CriticalSection to Mutex, recompile. But there are lots of mutexes in the system and these are potentially owned. Transforming unowned ones is trivial, but transforming owned ones is, I think, impossible. But at least in my system there are no owned mutexes or monitors. Frank (or anyone else), would you be interested in creating a replacement for Squeak's Monitor based on CriticalSection? Here are the two business methods: *CriticalSection methods for mutual exclusion* *critical:* aBlock "Evaluate aBlock protected by the receiver." ^self primitiveEnterCriticalSection ifTrue: [aBlock value] ifFalse: [aBlock ensure: [self primitiveExitCriticalSection]] *critical:* aBlock *ifLocked:* lockedBlock "*Answer the evaluation of aBlock protected by the receiver. If it is already in a critical* * section on behalf of some other process answer the evaluation of lockedBlock.*" ^self primitiveTestAndSetOwnershipOfCriticalSection ifNil: [lockedBlock value] ifNotNil:[:alreadyOwner| alreadyOwner ifTrue: [aBlock value] ifFalse: [aBlock ensure: [self primitiveExitCriticalSection]]] and the primitives: *CriticalSection methods for private-primitives* *primitiveEnterCriticalSection* "Primitive. The receiver must be unowned or owned by the current process to proceed. Answer if the process is owned by the current process." <primitive: 186> self primitiveFailed "In the spirit of the following" "[owner ifNil: [owner := Processor activeProcess. ^false]. owner = Processor activeProcess ifTrue: [^true]. self addLast: Processor activeProcess. Processor activeProcess suspend] valueUnpreemptively" *primitiveExitCriticalSection* "Primitive. Set te receiver to unowned and if any processes are waiting on the receiver then proceed the first one, indicating that the receiver is unowned." <primitive: 185> self primitiveFailed "In the spirit of the following" "[owner := nil. self isEmpty ifFalse: [process := self removeFirst. process resume]] valueUnpreemptively" *primitiveTestAndSetOwnershipOfCriticalSection* "Primitive. Attempt to set the ownership of the receiver. If the receiver is unowned set its owningProcess to the activeProcess and answer false. If the receiver is owned by the activeProcess answer true. If the receiver is owned by some other process answer nil." <primitive: 187> self primitiveFail "In the spirit of the following" "[owner ifNil: [owningProcess := Processor activeProcess. ^false]. owner = Processor activeProcess ifTrue: [^true]. ^nil] valueUnpreemptively" 2016-01-07 13:24 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> >> Hello. >> >> I hear about new Monitor implementation based on new primitives. >> Where to get it? >> > _,,,^..^,,,_ best, Eliot

Jan. 7, 2016