From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mail.toke.dk (Postfix) with ESMTPS id 8263E9B0DC4 for ; Mon, 31 Oct 2022 15:34:41 +0100 (CET) Authentication-Results: mail.toke.dk; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.a=rsa-sha256 header.s=Intel header.b=W6ObxtgB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1667226882; x=1698762882; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=1/9s7CWhJVq2t2k0cmR+pgj89lz/7OULjiOZcjFEIbk=; b=W6ObxtgBBCfvYk/hWiVLNKg/UTSc8KMjVAyAMoNTQDiwOv9dHYVT5fSV DbnpkC4Sj1Cptg6s02W2AiEiWGlQp1oQ1rI06SLQOmCMhunBPfYBQk/87 NCJGSIj0Qfj2gCHJ8Mdxt2zoUOZ1krR3V7CVtXyZOzHQktJy6qvpIJW3V HDeEb1xjB3g9Mzns6YXYJPitsxi0U274vPLviMB94Ls5Pr1/CegkPmvdR YG7mSCsZ3sRq+hluRJKPWHXmJbTG6r/BqYj34mkJ6T73RKiABSD6NTpkC lNZO4caaiMI3N3kDbUBu52GP6sd+puZbvWYdhhq3uo94+Arp2QnElfXqN w==; X-IronPort-AV: E=McAfee;i="6500,9779,10517"; a="306526603" X-IronPort-AV: E=Sophos;i="5.95,228,1661842800"; d="scan'208";a="306526603" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Oct 2022 07:31:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10517"; a="664796605" X-IronPort-AV: E=Sophos;i="5.95,228,1661842800"; d="scan'208";a="664796605" Received: from irvmail001.ir.intel.com ([10.43.11.63]) by orsmga008.jf.intel.com with ESMTP; 31 Oct 2022 07:30:59 -0700 Received: from newjersey.igk.intel.com (newjersey.igk.intel.com [10.102.20.203]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id 29VEUwgI001967; Mon, 31 Oct 2022 14:30:58 GMT From: Alexander Lobakin To: Stanislav Fomichev Date: Mon, 31 Oct 2022 15:29:07 +0100 Message-Id: <20221031142907.164469-1-alexandr.lobakin@intel.com> X-Mailer: git-send-email 2.38.1 In-Reply-To: <20221031142032.164247-1-alexandr.lobakin@intel.com> References: <20221027200019.4106375-1-sdf@google.com> <20221027200019.4106375-6-sdf@google.com> <31f3aa18-d368-9738-8bb5-857cd5f2c5bf@linux.dev> <1885bc0c-1929-53ba-b6f8-ace2393a14df@redhat.com> <20221031142032.164247-1-alexandr.lobakin@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Message-ID-Hash: JP7F2R7EHZFK6QVD3TWSX254QN26MKRL X-Message-ID-Hash: JP7F2R7EHZFK6QVD3TWSX254QN26MKRL X-MailFrom: alexandr.lobakin@intel.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Alexander Lobakin , Jesper Dangaard Brouer , Martin KaFai Lau , brouer@redhat.com, ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org, song@kernel.org, yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org, haoluo@google.com, jolsa@kernel.org, Jakub Kicinski , Willem de Bruijn , Anatoly Burakov , Magnus Karlsson , Maryam Tahhan , xdp-hints@xdp-project.net, netdev@vger.kernel.org, bpf@vger.kernel.org X-Mailman-Version: 3.3.5 Precedence: list Subject: [xdp-hints] Re: [RFC bpf-next 5/5] selftests/bpf: Test rx_timestamp metadata in xskxceiver List-Id: XDP hardware hints design discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: Alexander Lobakin Date: Mon, 31 Oct 2022 15:20:32 +0100 > From: Stanislav Fomichev > Date: Fri, 28 Oct 2022 11:46:14 -0700 > > > On Fri, Oct 28, 2022 at 3:37 AM Jesper Dangaard Brouer > > wrote: [...] > > I don't think __xdp_build_skb_from_frame is automagically solved by > > either proposal? > > It's solved in my approach[0], so that __xdp_build_skb_from_frame() Yeah sure forget to paste the link, why doncha? [0] https://github.com/alobakin/linux/commit/a43a9d6895fa11f182becf3a7c202eeceb45a16a > are automatically get skb fields populated with the metadata if > available. But I always use a fixed generic structure, which can't > compete with your series in terms of flexibility (but solves stuff > like inter-vendor redirects and so on). [...] > Thanks, > Olek Thanks, Olek