From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3C696C169C4 for ; Mon, 11 Feb 2019 07:52:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0CFA520811 for ; Mon, 11 Feb 2019 07:52:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="sUETfX17" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726814AbfBKHwU (ORCPT ); Mon, 11 Feb 2019 02:52:20 -0500 Received: from mail-ot1-f66.google.com ([209.85.210.66]:35175 "EHLO mail-ot1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725931AbfBKHwU (ORCPT ); Mon, 11 Feb 2019 02:52:20 -0500 Received: by mail-ot1-f66.google.com with SMTP id z19so11917711otm.2 for ; Sun, 10 Feb 2019 23:52:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=z7y9vXPgSa7ADEnYST5X0mfI2+9yfN8Gq6TIlgqr2xM=; b=sUETfX1798AEW++UeASIHaghOSwZXkOLIReVfinm3SE1fC4gvWzDNUtMQ4aYg+yGZr fB7qv49jI4P210GvMxjNM45dsg4U6ygqTmuWwTqdLHNzf5v3NXXuC8rWEgqh65LM+c10 Wc4LscMOVVEIPwhdNEJEC44IHZ1N0sfewOAczi4eDIaSSJn/dEix9mA6RUe6kGIIYlbu ntPFUrge3COy8SSib1bH0fT7AXS8fw7vBndNBcuT4rdWQV1VLMws/umSUWH1/m/MFY8E 66/4j+rtl1x4nmAwLjBDJ4xNOpEDF2PAvZZ/uj3UE0panWu7WrLSRTUGc17MbG310T9N V/Xg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=z7y9vXPgSa7ADEnYST5X0mfI2+9yfN8Gq6TIlgqr2xM=; b=RrAAZ3agVjJshiHm1EkVmQDGPL7UfCyjrfOcLcz2Xzu14OvPfeFr0q17guKYE19/vI JlwErdHWXKk2c9vE4RLmCXlNRqQlSmg7nKqLgl6TPug+l1PhhI59K8i0UJtdfS818S5o CA5CXJkDbHUiZkkBgQQpkxxAyopjCJffsq78kLpLhLh1Fbd3kagFJ7HABjnm1ARvIYB8 evQtFIaPpQdmDSSNOiqMDJAzrg58wqZMpAljRV6iPgZiDoIWM7OKdw48Z8E6k7NeuHc2 dZuEQShmQwDnLbntA2jxqSosbXTKE/wC2/lw7Ov+KifUtojOqzOUzcav14x8SaQsno+/ 1TxQ== X-Gm-Message-State: AHQUAubbBjKiUI2HpivCHqt/UW+munfL07ZsOgVM9KTAmaomyTo2bihc FsQToy0WZvpM9lYh38o/wFFnQbHJR+iOh3k6YC0= X-Google-Smtp-Source: AHgI3IZv5ewhU1D5aXMj4SM5M/RdpWI3CmmwoXoMVS5FZi5RGzxZW9ono40IkjSPg8FBFjC4j1VQm3zODkTgcqIKfGc= X-Received: by 2002:a9d:ecd:: with SMTP id 71mr18734733otj.155.1549871539395; Sun, 10 Feb 2019 23:52:19 -0800 (PST) MIME-Version: 1.0 References: <1549631126-29067-1-git-send-email-magnus.karlsson@intel.com> In-Reply-To: From: Magnus Karlsson Date: Mon, 11 Feb 2019 08:52:08 +0100 Message-ID: Subject: Re: [PATCH bpf-next v4 0/2] libbpf: adding AF_XDP support To: Jean-Mickael Guerin Cc: Magnus Karlsson , =?UTF-8?B?QmrDtnJuIFTDtnBlbA==?= , ast@kernel.org, Daniel Borkmann , Network Development , Jakub Kicinski , =?UTF-8?B?QmrDtnJuIFTDtnBlbA==?= , "Zhang, Qi Z" , Jesper Dangaard Brouer , xiaolong.ye@intel.com Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Mon, Feb 11, 2019 at 7:34 AM Jean-Mickael Guerin wrote: > > Hi Magnus, > > > * In a future release, I am planning on adding a higher level data > > plane interface too. This will be based around recvmsg and sendmsg > > with the use of struct iovec for batching, without the user having > > to know anything about the underlying four rings of an AF_XDP > > socket. There will be one semantic difference though from the > > standard recvmsg and that is that the kernel will fill in the iovecs > > instead of the application. But the rest should be the same as the > > libc versions so that application writers feel at home. > > You might consider recvmmsg() and sendmmsg() (bulk of multi segments packets?) Exactly :-). Spot on. /Magnus > Jean-Mickael