Yeah, I've come full circle back to the relative timeout point of view.
By grabbing a copy of jiffies at the beginning of the function the race
with preempt can be avoided.
> Now reading the SuS specifications I also like less and less our current
> kernel API of this sumbit_io, the SuS does exactly what I suggested
> originally that is aio_read/aio_write/aio_fsync as separate calls. So
> the merging effect mentioned by Ben cannot be taken advantage of by the
> kernel anyways because userspace will issue separate calls for each
Read it again. You've totally missed lio_listio. Also keep in mind what
happens with 4G/4G split for x86 which are needed to address the kernel
virtual memory starvation issues.
-- "You will be reincarnated as a toad; and you will be much happier." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/