Hello Dave, Below is a copy of the bk tree at: bk pull master.kernel.org:/home/bcrl/net-2.5 This tree adds the iocb parameter into the sendmsg and recvmsg operations within the network operations. so
The private area of an iocb for network operations contains a struct scm_cookie. The alternative is to allocate it via kmalloc when needed, but there isn't currently a way of identifying which networ
The private area of an iocb for network operations contains a struct scm_cookie. I know this. But the comment is wrong, when you say "for FOO" next to an include that means "I'm including this to ge
Hi, [patch etc. cut] I have a few questions about the way aio interacts with the socket locking and the consequences for atomicity of requests: Given two aio requests, A and B both for the same socke
The POSIX standard does not seem to require any ordering between requests, and some implementations take advantage of this by using threads to execute requests. That said, providing intra request ord
Hello! Kill it. It was not killed in 2.4 by plain luck, sorry, misfortune. However, I do not understand this. You need to pass forth and back SCM_RIGHTS is some way. It is quite dubious to make this
Hello, You actually do get to execute synchronously in the user's context the first time the function is entered to queue the operation, so collecting the credentials on entry and storing them for fu
Below is a copy of the bk tree at: bk pull master.kernel.org:/home/bcrl/net-2.5 Pulled, thanks. We can work out the issues Steve brought up independantly.