Experimental Physics and
Industrial Control System

"Jeff Hill" <[email protected]> · Thu, 1 Apr 2010 11:27:31 -0600

> Forgive my ignorance, but I think I am lacking some 
> context here.  What OSI interfaces are you developing?

I created some SMP safe osi atomic operator functions (increment, decrement,
etc) on the CVS main trunk - which were not included in the Bazaar main
trunk (which is branch off of R3.14). I mentioned these functions briefly in
my talk at the last EPICS meeting. The implementation is based on the resent
GNU compiler intrinsic functions, and when that compiler isn?t available is
based on OS primitives. Old vxWorks 68k doesn?t need anything special as its
increment function is atomic. The PPC vxWorks can just use intLock. SMP
vxWorks has the new gcc. RTEMS probably will also. I have implementations
also for Solaris and MS WIN32.

Jeff
______________________________________________________
Jeffrey O. Hill           Email        [email protected]
LANL MS H820              Voice        505 665 1831
Los Alamos NM 87545 USA   FAX          505 665 5107

Message content: TSPA

> -----Original Message-----
> From: Davidsaver, Michael [mailto:[email protected]]
> Sent: Thursday, April 01, 2010 8:06 AM
> To: Jeff Hill
> Subject: RE: naming the operating system independence layer
> 
> Jeff,
> 
> Forgive my ignorance, but I think I am lacking some context here.  What
> OSI interfaces are you developing?
> 
> Michael
> 
> > -----Original Message-----
> > From: Jeff Hill [mailto:[email protected]]
> > Sent: Wednesday, March 31, 2010 5:48 PM
> > To: 'EPICS core-talk'
> > Cc: 'Eric Norum'; 'Andrew Johnson'; Janet Anderson; 'Ralph Lange';
> > Davidsaver, Michael
> > Subject: naming the operating system independence layer
> >
> >
> > All,
> >
> > As I create new operating system independent interfaces it would be
> > best for
> > them to be placed in a C++ namespace. Currently I have, nested inside
> > the
> > namespace "epics", a namespace "osi" standing for "operating system
> > independent". However, perhaps there is some dismay related to the name
> > "osi", as an acronym for "operating system independent", because it is
> > of
> > course similar to other acronyms; for example there are of course "open
> > system interconnect" and "open source imitative" in common use. The
> > name
> > "osd" is also commonly in use today in the EPICS distribution standing
> > for
> > "operating system dependent".
> >
> > Other options:
> > o epics :: osl - standing for "operating system liberated"
> >
> > At this juncture, this issue remains quite easy to fix in the source
> > code as
> > the new namespace is minimally populated.
> >
> > Comments?
> >
> > Jeff
> > ______________________________________________________
> > Jeffrey O. Hill           Email        [email protected]
> > LANL MS H820              Voice        505 665 1831
> > Los Alamos NM 87545 USA   FAX          505 665 5107
> >
> > Message content: TSPA
> >
> >

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System