Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751666AbdG1D3B (ORCPT ); Thu, 27 Jul 2017 23:29:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59258 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751570AbdG1D3A (ORCPT ); Thu, 27 Jul 2017 23:29:00 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 47B83C0608E4 Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=jasowang@redhat.com Subject: Re: [PATCH net-next 3/3] tap: XDP support To: Jakub Kicinski Cc: davem@davemloft.net, mst@redhat.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <1501147533-12368-1-git-send-email-jasowang@redhat.com> <1501147533-12368-4-git-send-email-jasowang@redhat.com> <20170727201338.65d56b2a@cakuba.netronome.com> From: Jason Wang Message-ID: <7d1cb7bf-43c1-3993-be00-04e4676dd917@redhat.com> Date: Fri, 28 Jul 2017 11:28:54 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170727201338.65d56b2a@cakuba.netronome.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Fri, 28 Jul 2017 03:29:00 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2247 Lines: 68 On 2017年07月28日 11:13, Jakub Kicinski wrote: > On Thu, 27 Jul 2017 17:25:33 +0800, Jason Wang wrote: >> This patch tries to implement XDP for tun. The implementation was >> split into two parts: >> >> - fast path: small and no gso packet. We try to do XDP at page level >> before build_skb(). For XDP_TX, since creating/destroying queues >> were completely under control of userspace, it was implemented >> through generic XDP helper after skb has been built. This could be >> optimized in the future. >> - slow path: big or gso packet. We try to do it after skb was created >> through generic XDP helpers. >> >> XDP_REDIRECT was not implemented, it could be done on top. >> >> xdp1 test shows 47.6% improvement: >> >> Before: ~2.1Mpps >> After: ~3.1Mpps >> >> Suggested-by: Michael S. Tsirkin >> Signed-off-by: Jason Wang >> @@ -1008,6 +1016,56 @@ tun_net_get_stats64(struct net_device *dev, struct rtnl_link_stats64 *stats) >> stats->tx_dropped = tx_dropped; >> } >> >> +static int tun_xdp_set(struct net_device *dev, struct bpf_prog *prog, >> + struct netlink_ext_ack *extack) >> +{ >> + struct tun_struct *tun = netdev_priv(dev); >> + struct bpf_prog *old_prog; >> + >> + /* We will shift the packet that can't be handled to generic >> + * XDP layer. >> + */ >> + >> + old_prog = rtnl_dereference(tun->xdp_prog); >> + if (old_prog) >> + bpf_prog_put(old_prog); >> + rcu_assign_pointer(tun->xdp_prog, prog); > Is this OK? Could this lead to the program getting freed and then > datapath accessing a stale pointer? I mean in the scenario where the > process gets pre-empted between the bpf_prog_put() and > rcu_assign_pointer()? Will call bpf_prog_put() after rcu_assign_pointer(). > >> + if (prog) { >> + prog = bpf_prog_add(prog, 1); >> + if (IS_ERR(prog)) >> + return PTR_ERR(prog); >> + } > I don't think you need this extra reference here. dev_change_xdp_fd() > will call bpf_prog_get_type() which means driver gets the program with > a reference already taken, drivers does have to free that reference when > program is removed (or device is freed, as you correctly do). I see, will drop this in next version. Thanks. > >> + return 0; >> +} >> +