From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mail.toke.dk (Postfix) with ESMTPS id C1541969417 for ; Mon, 16 May 2022 16:42:57 +0200 (CEST) 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=aBRUvNBR DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1652712178; x=1684248178; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=a+Ao1BlLPw3VidNpDfNmoPoWqMemO/83lebBpSAqDPE=; b=aBRUvNBROKt9TxpakxhE3Cxn+RIdFi8tt/si1cd+9H1OrvoG7Os6z+Pe PsMG0zswwte1pmTBON2uJ6pRYjnzCCi6OS/aYjOgt0X7h8VJySelAavf+ +EgOcKyFDycIRBFS8LdsOFk8d5qwA3DiVZw4U8sXflYEIHhJGvHFydX4e XEXIjSAFzUqKZztqK//RMnbDBeDIqPWbmtz8oZl7fdi+DYr+jPM5PmoHC EU2V7XQEpeQPD98x+sQkL5DZm7b5pn0LiYBRqsFxJq7XVOVVDckDCV4wc K4SuZKEVeUN2E/BVCinmeZxyaFSPWb1/m1/U0eNa8uTSJ6VwHOBHg34jn w==; X-IronPort-AV: E=McAfee;i="6400,9594,10348"; a="270799480" X-IronPort-AV: E=Sophos;i="5.91,230,1647327600"; d="scan'208";a="270799480" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 May 2022 07:41:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.91,230,1647327600"; d="scan'208";a="638271230" Received: from irvmail001.ir.intel.com ([10.43.11.63]) by fmsmga004.fm.intel.com with ESMTP; 16 May 2022 07:41:53 -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 24GEfqrU008361; Mon, 16 May 2022 15:41:52 +0100 From: Alexander Lobakin To: Jesper Dangaard Brouer Date: Mon, 16 May 2022 16:41:35 +0200 Message-Id: <20220516144135.11132-1-alexandr.lobakin@intel.com> X-Mailer: git-send-email 2.35.3 In-Reply-To: References: MIME-Version: 1.0 Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Message-ID-Hash: 2AEIQIP24GMJ3CNLQRHZY7UXY7NJYQJ6 X-Message-ID-Hash: 2AEIQIP24GMJ3CNLQRHZY7UXY7NJYQJ6 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 , brouer@redhat.com, Larysa Zaremba , "xdp-hints@xdp-project.net" X-Mailman-Version: 3.3.5 Precedence: list Subject: [xdp-hints] Re: XDP-hints presentation at LLC2022 List-Id: XDP hardware hints design discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: Jesper Dangaard Brouer Date: Mon, 16 May 2022 15:58:06 +0200 > Hi XDP-hints community, Hey! > > Gave this talk[1] on Friday (13 May) "XDP hints via BPF" at Lund Linux > Con. In the talk we are proposing several *possible* solutions, with > "pros" and "cons". We are open to new ideas, proposals and critique. > > I will play with implementing some of these ideas and to see if they > pan-out. I want to acknowledge that Alexander Lobakin (+ co-authors) > also have started coding on solutions here[3]. Lets see if we can > collaborate and find a solution we can all agree on. Nice catch about "it makes it possible to make NIC driver L2 only" -- it's not present in the current code, but we're thinking of this for some time already :) Re collaborate -- I'm expecting the first RFC to hit internal review in 2-3 weeks, hope it will get posted to LKML soon after that. GH tree should be finalized this week, so you could start playing. > > --Jesper > > > [1] Slide PDF: > https://github.com/xdp-project/xdp-project/blob/master/conference/LLC2022/xdp_hints_hw_metadata-final.pdf > > [2] Slide source: > https://github.com/xdp-project/xdp-project/tree/master/conference/LLC2022 > > [3] https://github.com/alobakin/linux/commits/xdp_hints Thanks, Al