>I believe you can specify hash storage by passing the appropriate DBM flags
>when you do DBI->connect(). Use the flags your DBM implementation expects and
>pass them as specified in the DBD::DBM docs.
I have been over the docs several times, as well as the source code,
and am knee-deep in writing a patch (on the offhand suggestion of Tim
Bunce on the Class::DBI list).
If DBD::DBM supports hashrefs as values the same way it supports
arrayrefs as values, I am _really_ missing something.
Needless to say, I saw no such flags. If they exist I would love to
see them, so I can chuck this patch.
[RFC 1/1] Char: mxser_new, fix recursive locking ...patch attached - I am not able to reproduce the lockup with this patch. ... determine whether the lock should be re-aquired or not. ... before calling all involved mxser_ routines. ... unsigned long flags;... (Linux-Kernel)
[RFC] [PATCH] Per-mountpoint read-only and noatime revisited ... macro that makes use of the new flags.... to the IS_* macro call are changed to pass the struct vfsmount*... Furthermore, this patch adds the new functionality as new mount flags, ... (Linux-Kernel)
Re: *at family of syscalls in FreeBSD ... *at_getwd- In addition to your parameters, we also pass in the flags... the subfile container if the user passed in O_XATTR (solaris uses this ... fd if you pass in an absolute path (I haven't looked at draft posix ... I am willing to adjust my patch with either the wrapping idea and/or the flags thing. ... (freebsd-arch)
Re: CPU Hotplug broken -mm5 onwards ... > I found that removing the lock in exec path has other consequences ... Found that lockless migration of execing task is _extremely_ racy. ... Anyway patch below addresses the above races. ... runqueue_t *rq; unsigned long flags;... (Linux-Kernel)
