From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f177.google.com (mail-wr0-f177.google.com [209.85.128.177]) by dpdk.org (Postfix) with ESMTP id E2EC111D4 for ; Mon, 13 Feb 2017 23:14:43 +0100 (CET) Received: by mail-wr0-f177.google.com with SMTP id o16so160223823wra.1 for ; Mon, 13 Feb 2017 14:14:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=hxErzv84I+QLJWf9X1DL2npDH4DXAMagZnKTnig7SpI=; b=TT/sxhWfE9FYI+93eKXJUvayeVZKpTbnrlumGPx6TvDCJU7q0CKxjjDvM0btXim027 kgamQQg9iqs84E7G1Z2/R780k50jgfdAxu6fo8YIomF5WpjM/NrmWU+8qIv/nMBd+ifA uuKBWYUOcDIZHa2h+ZFeX+7nqI5jsADuhfuI+f0x5CW0vVgOw9CL1uFjzGbYkzynPdFh HyaJScOL7Dtv6Nh1BD6hJNiv9uPG/ykFC3f1Kn0z4X9gnTU2qaHyVK5E0NeZiym4PYIE Z80sbls47Xs/M9Aov8nU91sjN5gZYcgEpp/DyMn+EuLNlqMlg6jOUe5QR9lrjCEjWSZ4 /MbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=hxErzv84I+QLJWf9X1DL2npDH4DXAMagZnKTnig7SpI=; b=GOYJ5bRI35gSCAGqEJaVbhp61v0IXb0G79k9PYPGyfM/CgbHiO/2vwOcjBtq/A8i5M l/vieBhRhB5KlPOxtDK1Q60AUhVyQhDLz3PFRxEs5SFo8/xYF+zZc0Fsaf/VzPeF7ZY2 g+FMv4fngYqubwHapxdnjGi5a7qRXH8ZDDrAa4o/E4lvWymdKg8PVmDbfHlGiRvGRzaP +sjzKdjrjjjsWmWtFu76gwM34zQh0bzuI3P24x/hUZgjsCJJ+dt9E659vI0hfLmDxiwV aTC3k5WemHo7YD9en1BqH9tH0Z7khFvZ31wr65x30LdCNJ8E35grP+Z/I1KkiCdY8l/c u9xA== X-Gm-Message-State: AMke39n3K8bizEW1SCy3QrK5ZLYqeYjGUUr7MWkF5RxvLY2FoNjKHjLTqkste615TiR/Qhmj X-Received: by 10.223.168.111 with SMTP id l102mr21583545wrc.150.1487024083620; Mon, 13 Feb 2017 14:14:43 -0800 (PST) Received: from ?IPv6:2a01:e35:8a8e:1b70:69af:1558:3bc1:4e8c? ([2a01:e35:8a8e:1b70:69af:1558:3bc1:4e8c]) by smtp.gmail.com with ESMTPSA id m26sm12295283wrb.68.2017.02.13.14.14.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Feb 2017 14:14:42 -0800 (PST) To: Sameera.Netala@cavium.com References: <18142536.l3p9GNq4yZ@xps13> Cc: Ferruh Yigit , "users@dpdk.org" , "Fastabend, John R" From: Vincent JARDIN Organization: www.6wind.com Message-ID: <278979a8-80c9-0f24-7aba-f92117235e77@6wind.com> Date: Mon, 13 Feb 2017 23:14:36 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <18142536.l3p9GNq4yZ@xps13> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] Is PF-only driver allowed to upstream into dpdk? X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2017 22:14:44 -0000 >> I am currently working on a non-nic mode user space PCI driver >> which processes custom packets from OCTEON 7xxx processor. As >> per the requirements, DPDK is the best way to achieve this. >> >> Though I have seen few designs and sources that talk about dpdk >> pf drivers, I am interested to know if such a driver with pf-only >> support and which doesn't involve virtual functions will be allowed >> to upstream into DPDK sources. > There is no problem with PF only drivers, and there are already samples > of it in the project. > > As long as driver is open source and for data path, it is good for > upstream. Please feel free to upstream your driver when it is ready. > > The discussion about DPDK PF drivers was about if DPDK PF driver should > be in control path or not, this is high level project scope discussion. It is about diverging with the Linux kernel's PF. It is not acceptable, from a VF point of view to have different behaviors. Then, about this specific request regarding Octeon's PF, your description is not clear enough to comment deeply about it. Best regards, Vincent