Who Should See the Film 'Patent Absurdity'? - Pick Your Brain

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Who Should See the Film 'Patent Absurdity'? - Pick Your Brain
# 1  
Old 05-24-2010
Who Should See the Film 'Patent Absurdity'? - Pick Your Brain

I have a request from End Softare Patents' Ciarán O'Riordan. He'd like your help.
He says VC good guy Brad Feld is interested in in mailing out copies of the film Patent Absurdity (Full title: Patent Absurdity: How software patents broke the system) to 200 people -- politicians,influential people in companies, policy setters at standards groups, andwhoever will be influential in the debate the breaks out post-Bilski -- and he'd like to have some help from you coming up with a list of who best to send to.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Linux

micro film scanner

epson microfilm 500 scsi: Is there any way to make this work under linux ? I'm using pclinuxos, it shows the machine in the device panel as sg2 and lists the machine , so Im guessing the kernel knows what it is, but I can't view it as a scanner or capture or input device . What catagory does... (4 Replies)
Discussion started by: tom1200
4 Replies
Login or Register to Ask a Question
PSERIALIZE(9)						   BSD Kernel Developer's Manual					     PSERIALIZE(9)

NAME
pserialize -- passive serialization mechanism SYNOPSIS
#include <sys/pserialize.h> pserialize_t pserialize_create(void); void pserialize_destroy(pserialize_t psz); int pserialize_read_enter(void); void pserialize_read_exit(int s); void pserialize_perform(pserialize_t psz); DESCRIPTION
Passive serialization is a reader / writer synchronisation mechanism designed for lock-less read operations. The read operations may happen from software interrupt at IPL_SOFTCLOCK. FUNCTIONS
pserialize_create() Allocate a new synchronisation object. pserialize_destroy() Destroy the synchronisation object. No synchronisation activity should happen at this point. pserialize_read_enter() Enter the critical path of the reader side. Returns an IPL value, which must be passed to pserialize_read_exit(9). Protected code path is not allowed to block. pserialize_read_exit() Exit the critical path of the reader side. Takes the IPL value returned by pserialize_read_enter(9). pserialize_perform() Perform the passive serialization on the writer side. Passing of this function ensures that no readers are in action. Writers must be additionally serialized with a separate mechanism, e.g. mutex(9). Operation blocks and it may only be performed from thread context. EXAMPLES
Typical code fragment in the writer side: mutex_enter(&writer_psz_lock); /* * Perform the updates (e.g. remove data items from a list). */ ... pserialize_perform(object->psz); /* * At this point it is safe to destroy old data items. */ mutex_exit(&writer_psz_lock); CODE REFERENCES
The pserialize is implemented within the file sys/kern/subr_pserialize.c. SEE ALSO
membar_ops(3), condvar(9), mutex(9), rwlock(9) Hennessy, et al., Passive serialization in a multitasking environment, US Patent and Trademark Office, US Patent 4809168, February 28, 1989. HISTORY
Passive serialization mechanism first appeared in NetBSD 6.0. BSD
July 30, 2011 BSD