Article View: comp.sys.sequent
Article #232A technical shmalloc question.
From: Simon Marshall
Date: Thu, 03 Sep 1992 16:03
Date: Thu, 03 Sep 1992 16:03
17 lines
1241 bytes
1241 bytes
Hi. I'm trying to work out bottlenecks. Shmalloc must lock in some
way, in order to allocate unique blocks, even when calls to shmalloc are
made concurrently.
Does anyone know whether shmalloc locks *all* processes, within its
body (ie. whatever other processes are doing), using something like
m_lock(), or does shmalloc lock only within itself, allowing other
processes to continue unless they call shmalloc.
Please can anyone let me know? Does anyone know?!
Thanks, in advance, Simon.
_______________________________________________________________________________
Simon Marshall, Dept. of Computer Science, University of Hull, Hull HU6 7RX, UK
"Football isn't about life and death. It's more important than that." Bill
Email: S.Marshall@Hull.ac.uk Phone: +44 482 465181 Fax: 466666 Shankley
Technical Details
Message-ID:
<9209031506.AA23319@ucbvax.Berkeley.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!ogicse!uwm.edu!linac!att!ucbvax!sequent.cc.hull.ac.uk!S.MarshallShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!ogicse!uwm.edu!linac!att!ucbvax!sequent.cc.hull.ac.uk!S.Marshall From: S.Marshall@sequent.cc.hull.ac.uk (Simon Marshall) Newsgroups: comp.sys.sequent Subject: A technical shmalloc question. Message-ID: <9209031506.AA23319@ucbvax.Berkeley.EDU> Date: 3 Sep 92 16:03:17 GMT Article-I.D.: ucbvax.9209031506.AA23319 Sender: usenet@ucbvax.BERKELEY.EDU Lines: 17