William Lee Irwin III wrote:
I'm ambivalent now I guess. I'm not wild about bh's in the first place,
so infecting core code with new dependencies on them doesn't sound hot,
though I still can't help cringing at using a bitflag in the first bh
in the list to protect against concurrent teardown of the bh list,
which relies on the setup/teardown patterns.
It's not quite as bad as that - there will be no teardown while
any of the buffers are still in flight. The lock is simply to
protect concurrent completion of requests, it could just as
easily go in the last bh.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
