From: John Fastabend <john.fastabend@gmail.com>
To: tndave <tushar.n.dave@oracle.com>,
bjorn.topel@gmail.com, jasowang@redhat.com, ast@fb.com,
alexander.duyck@gmail.com, brouer@redhat.com
Cc: john.r.fastabend@intel.com, netdev@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] rx zero copy interface for af_packet
Date: Tue, 31 Jan 2017 21:09:07 -0800 [thread overview]
Message-ID: <58916D73.7040303@gmail.com> (raw)
In-Reply-To: <4f68b864-8b9d-a57f-0843-30f613260b17@oracle.com>
On 17-01-31 11:39 AM, tndave wrote:
>
>
> 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!
>
Yes, I'll try to create another RFC in a week or two. Thanks.
> -Tushar
prev parent reply other threads:[~2017-02-01 5:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 21:33 [RFC PATCH 0/2] rx zero copy interface for af_packet John Fastabend
2017-01-27 21:33 ` [RFC PATCH 1/2] af_packet: direct dma for packet ineterface John Fastabend
2017-01-30 18:16 ` Jesper Dangaard Brouer
2017-01-30 21:51 ` John Fastabend
2017-01-31 1:31 ` Willem de Bruijn
2017-02-01 5:09 ` John Fastabend
2017-03-06 21:28 ` chetan loke
2017-01-31 12:20 ` Jesper Dangaard Brouer
2017-02-01 5:01 ` John Fastabend
2017-02-04 3:10 ` Jason Wang
2017-01-27 21:34 ` [RFC PATCH 2/2] ixgbe: add af_packet direct copy support John Fastabend
2017-01-31 2:53 ` Alexei Starovoitov
2017-02-01 4:58 ` John Fastabend
2017-01-30 22:02 ` [RFC PATCH 0/2] rx zero copy interface for af_packet David Miller
2017-01-31 16:30 ` Sowmini Varadhan
2017-02-01 4:23 ` John Fastabend
2017-01-31 19:39 ` tndave
2017-02-01 5:09 ` John Fastabend [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58916D73.7040303@gmail.com \
--to=john.fastabend@gmail.com \
--cc=alexander.duyck@gmail.com \
--cc=ast@fb.com \
--cc=bjorn.topel@gmail.com \
--cc=brouer@redhat.com \
--cc=jasowang@redhat.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=tushar.n.dave@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.