:Again, I think it comes down to the fact that memory allocation APIs
:typically offer choices to the consumer: block if the resources aren't
:available, or fail. My mood swings a bit back and forth as to what the
:ideal strategy would/should be at the lowest level, but I think as you
:move up the
:...
:Moving towards message passing helps to structure the code to avoid
:sharing of this sort, although it's not the only way to motivate that sort
:of change. I'm a big fan of the change in -CURRENT to use td->td_cred as
:a read-only thread-local credential reference and avoid synchronization
(Subject changed to reflect the fact that it contains useful technical
content and banter, resulting in a hijacking of the thread; hope no one
minds)
On Sat, 25 Oct 2003, Matthew Dillon wrote:
> Yes. I'm not worried about BPF, and ucred is easy since it is
> already 95% of the way there
3 matches
Mail list logo
