Re: [patch v3] splice: fix race with page invalidation

Evgeniy Polyakov
2008-07-31T10:27:47Z

On Thu, Jul 31, 2008 at 07:12:01AM +0100, Jamie Lokier (jamie@shareable.org) wrote:
> The obvious mechanism for completion notifications is the AIO event
> interface. I.e. aio_sendfile that reports completion when it's safe
> to modify data it was using. aio_splice would be logical for similar
> reasons. Note it doesn't mean when the data has reached a particular
> place, it means when the pages it's holding are released. Pity AIO
> still sucks ;-)

It is not that simple: page can be held in hardware or tcp queues for
a long time, and the only possible way to know, that system finished
with it, is receiving ack from the remote side. There is a project to
implement such a callback at skb destruction time (it is freed after ack
from the other peer), but do we really need it? System which does care
about transmit will implement own ack mechanism, so page can be unlocked
at higher layer. Actually page can be locked during transfer and
unlocked after rpc reply received, so underlying page invalidation will
be postponed and will not affect sendfile/splice.

> Btw, Windows had this since forever, it's called overlapped
> TransmitFile with an I/O completion event. Don't know if it's any
> good though ;-)

There was a linux aio_sendfile() too. Google still knows about its
numbers, graphs and so on... :)

--
Evgeniy Polyakov