Never mind. It protects some on-memory data which I don't know.
(Why do I lock lots of things to read read-only ROM data? I wish
VFS/BIO were written in Haskell...)
Matt,
On 2010-11-13 04:17, Matt Thomas wrote:
The VAX now has a fast non-MP emulation of atomic_cas so that should be
less of an issue.
I looked at this code, as well as your musings about the design. Did you
miss one step in there, or did I miss something?
I thought that we needed to
On Nov 20, 2010, at 12:25 AM, Johnny Billquist wrote:
Matt,
On 2010-11-13 04:17, Matt Thomas wrote:
The VAX now has a fast non-MP emulation of atomic_cas so that should be
less of an issue.
I looked at this code, as well as your musings about the design. Did you miss
one step in
On Apr 12, 5:11pm, David Holland wrote:
} On Fri, Nov 19, 2010 at 12:33:00AM -0800, John Nemeth wrote:
}.prop is short for proplib or property list. It also made
} coding easier as s/.kmod/.prop/ doesn't change the length of the path.
} Anyways, I have received several private
On Sat, Nov 20, 2010 at 07:50:03PM -0800, John Nemeth wrote:
} embed the property info in the module file itself?
That may or may not make more sense, but it would require a lot
more work (i.e. inventing a tool to extract them, edit them, and insert
them; and modifying the module
