XDP hardware hints discussion mail archive
 help / color / mirror / Atom feed
From: Alexander Lobakin <alexandr.lobakin@intel.com>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>
Cc: Alexander Lobakin <alexandr.lobakin@intel.com>,
	brouer@redhat.com, Larysa Zaremba <larysa.zaremba@intel.com>,
	"xdp-hints@xdp-project.net" <xdp-hints@xdp-project.net>
Subject: [xdp-hints] Re: XDP-hints presentation at LLC2022
Date: Mon, 16 May 2022 16:41:35 +0200	[thread overview]
Message-ID: <20220516144135.11132-1-alexandr.lobakin@intel.com> (raw)
In-Reply-To: <d711e4de-7a2c-2e22-266a-455803890b34@redhat.com>

From: Jesper Dangaard Brouer <jbrouer@redhat.com>
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

  reply	other threads:[~2022-05-16 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 13:58 [xdp-hints] " Jesper Dangaard Brouer
2022-05-16 14:41 ` Alexander Lobakin [this message]
2022-06-14 10:40   ` [xdp-hints] " Bezdeka, Florian
2022-06-15  7:45     ` Jesper Dangaard Brouer
2022-06-15 10:19       ` Alexander Lobakin
2022-07-04 13:07       ` Bezdeka, Florian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.xdp-project.net/postorius/lists/xdp-hints.xdp-project.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220516144135.11132-1-alexandr.lobakin@intel.com \
    --to=alexandr.lobakin@intel.com \
    --cc=brouer@redhat.com \
    --cc=jbrouer@redhat.com \
    --cc=larysa.zaremba@intel.com \
    --cc=xdp-hints@xdp-project.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox