Working on vnode sequencing and locking - HEAD will destabilize for a little bit
csaba.henk at creo.hu
Thu Aug 10 04:27:23 PDT 2006
On 2006-08-09, Matthew Dillon <dillon at xxxxxxxxxxxxxxxxxxxx> wrote:
> And, poof, no more indefinite blocking states in the kernel for NFS or
> for the upcoming userland VFS or clustering.
> There will be fine-grained range locks to maintain UNIX atomicy
> requirements, but since they aren't going to be hard locks they won't
> prevent basic things like ^C from working properly.
Btw, what does "^C working properly" mean? AFAIK SUS says/implies that
filesystem related syscalls shouldn't be interruptible, with the
exception of read and write.
More information about the Kernel