[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4f68b864-8b9d-a57f-0843-30f613260b17@oracle.com>
Date: Tue, 31 Jan 2017 11:39:16 -0800
From: tndave <tushar.n.dave@...cle.com>
To: John Fastabend <john.fastabend@...il.com>, bjorn.topel@...il.com,
jasowang@...hat.com, ast@...com, alexander.duyck@...il.com,
brouer@...hat.com
Cc: john.r.fastabend@...el.com, netdev@...r.kernel.org
Subject: Re: [RFC PATCH 0/2] rx zero copy interface for af_packet
On 01/27/2017 01:33 PM, John Fastabend wrote:
> This is an experimental implementation of rx zero copy for af_packet.
> Its a bit rough and likely has errors but the plan is to clean it up
> over the next few months.
>
> And seeing I said I would post it in another thread a few days back
> here it is.
This sounds good (believe me I have been thinking along the lines :)
From driver Rx side, we always premap RX buffers so best to map them to
shmem for PF_PACKET sockets.
Also, I like the idea that user can put selected queue (may be queues in
future?) to PF_PACKET mode keeping rest of the queues as it is.
Zero copy and removing skb setup & processing overhead on RX certainly
makes things faster and help latency. Zero copy is good on Tx however
without skb should we figure out how to use segmentation and checksum
offloading features of HW. Can this be considered in tpacket V4 hdr!
-Tushar
Powered by blists - more mailing lists