Re: [PATCH][RFC 23/23]: Support for zero-copy TCP transmit of user space data

Vladislav Bolkhovitin
2008-12-12T19:27:21Z

James Bottomley wrote:
> On Thu, 2008-12-11 at 21:16 +0300, Vladislav Bolkhovitin wrote:
>> Hi Evgeniy,
>>
>> Evgeniy Polyakov wrote:
>>> Hi Vladislav.
>>>
>>> On Wed, Dec 10, 2008 at 10:04:36PM +0300, Vladislav Bolkhovitin (vst@vlnb.net) wrote:
>>>> In the chosen approach new optional field void *net_priv was added to
>>>> struct page. It is enclosed by
>>> There is a huge no-no in networking land on increasing skb.
>>> Reason is simple every skb will carry potentially unneded data as long
>>> as given option is enabled, and most of the time it will.
>>> To break this barrier one has to have (I wanted to write ego, but then
>>> decided to replace it with mojo) so huge reason to do this, that it is
>>> almost impossible to have.
>>>
>>> Something tells me that increasing page structure with 8 bytes because
>>> of zero-copy iscsi transfer is not that great idea, since basically every
>>> user out there will have it enabled in the distro config and will waste
>>> noticeble amount of ram.
>> The waste will be only 0.2% of RAM or 2MB per 1GB. Not much. Perhaps,
>> not noticeable for an average user of distro kernels at all. Embedded
>> people, who count each byte, almost always don't need iSCSI, so won't
>> have any problems to disable
>> TCP_ZERO_COPY_TRANSFER_COMPLETION_NOTIFICATION option.
>
> Actually, there are several other considerations:
>
> 1. struct page is a lowmem structure, so increasing its size
> becomes problematic on x86 PAE systems.
> 2. The current 64 bit struct page seems to be exactly pushing a
> cacheline boundary. Increasing it so it spills over will have a
> performance impact

This is why I suggest to have
CONFIG_TCP_ZERO_COPY_TRANSFER_COMPLETION_NOTIFICATION disabled in
general kernels. ISCSI-SCST will still work with almost no performance
loss for in-kernel backend and people would better recompile kernel,
then patch it, then recompile.

> It's the performance problems that will be most critical, I suspect, so
> you'll need mm people buy in for doing this.

I'll ask in linux-mm, thanks for the suggestion.

> One thing that leaps immediately to mind is that you could isolate this
> to the net layer by putting it in skb_frag_struct. However, such a move
> would require a proper API for this in net ...

To have net_priv analog in skb was the first idea I was tried. But I
quickly gave up, because it would required that all the pages in each
skb_frag_struct be from the same originator, i.e. with the same
net_priv. It is unpractical to change all the operations with skb's to
forbid merging them, if they have different net_priv. There are too many
such places in very not obvious code pieces.

> right now it looks like
> you're using the struct page addition to carry this information from
> SCSI to net, which is a bit of a layering violation.

I don't think there is any layering violation here. Just lower layer
notifies upper layer that transmission of a page has finished. It's done
a bit not straightforward, but still basically the same as, for
instance, on_free_cmd() callbacks which SCST core uses to notify target
drivers and dev handlers that the corresponding command is about to be
freed, so they can free associated with it data as well.

Thanks,
Vlad