XDP-Newbies Archive mirror
 help / color / mirror / Atom feed
From: Magnus Karlsson <magnus.karlsson@gmail.com>
To: "Le, Ba Que" <b.le@tu-berlin.de>
Cc: "xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>,
	"bjorn.topel@gmail.com" <bjorn.topel@gmail.com>,
	"magnus.karlsson@intel.com" <magnus.karlsson@intel.com>
Subject: Re: question on contributing to the xdp project
Date: Tue, 9 May 2023 15:11:21 +0200	[thread overview]
Message-ID: <CAJ8uoz1pkOv0kJNKwOQtZ5-8boQKQ6J-ZyU01K4NdqRXj3k-eg@mail.gmail.com> (raw)
In-Reply-To: <3feb89faadcb449881f92dc690049076@tu-berlin.de>

On Tue, 9 May 2023 at 15:07, Le, Ba Que <b.le@tu-berlin.de> wrote:
>
> Hi,
>
> The bpf-examples is actually my targeted repo instead of xdp-tutorial (more up-to-date and better maintained).
>
> Can you give me the tutorial for the process since I'm new to it? First and foremost: I can't 100% guarantee the accuracy of the content, especially the documentation and explanations included with the programs. I understand that time and interest will be the deciding factors here, but it would be very nice if a senior member could give advice/correction/support during development. Secondly, code quality. Should the code be pre-reviewed by a senior supervisor to avoid unnecessary reviews of clumsy code, or can I proceed with a normal pull request?

Just send a pull request so we can review it. We are nice people so do
not worry :-).

Thanks: Magnus

>
> Best
>
> Que Le
>
> ________________________________
> Von: Magnus Karlsson <magnus.karlsson@gmail.com>
> Gesendet: Dienstag, 9. Mai 2023 14:27:53
> An: Le, Ba Que
> Cc: xdp-newbies@vger.kernel.org; bjorn.topel@gmail.com; magnus.karlsson@intel.com
> Betreff: Re: question on contributing to the xdp project
>
> On Tue, 9 May 2023 at 12:58, Le, Ba Que <b.le@tu-berlin.de> wrote:
> >
> > Hello,
> >
> >
> > I am a computer science master student at the TU Berlin and currently writing my Master Thesis.
> > I have been working on the AF_XDP socket for some time and would like to use the AF_XDP as the basis for my master thesis topic, which is multipath tunneling with XDP socket (may be changed in the future, depends on my supervisors).
> > While I was prototyping the thesis, I found that some of my code can be very useful for new people who want to learn and use the xdp socket.
> >
> > The code pieces mentioned are about:
> >
> > - UDP packet sender and receiver. These are ready-to-use programs. (Possibly be useful for requests by https://github.com/xdp-project/xdp-tutorial/issues/307 and https://github.com/xdp-project/xdp-tutorial/issues/307)
> > - Multiple independent AF_XDP sockets bind on multiple interfaces. I used it to test the possibility of using AF_XDP for multiple path tunneling. This will demonstrate how to setup and configure multiple sockets without UMEM sharing, and reading and writing UDP packets on these sockets.
> >
> > I imagine these examples might fit the XDP project's long term TODO "Adding AF_XDP support to relevant userspace programs" (https://xdp-project.net/#Adding-AF_XDP-support-to-relevant-userspace-programs).
> >
> > These programs will be submitted with detailed instruction and explanation.
> >
> > Please let me know your thoughts about the proposal.
>
> Hi,
>
> If you have good examples to contribute, that would be great. Maybe
> they would be a good fit for the bpf-examples repo.
>
> https://github.com/xdp-project/bpf-examples
>
> /Magnus
>
> > Best
> > Que Le
> >
> >

      parent reply	other threads:[~2023-05-09 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1192ed3a86ef4ef19e25a0864ede7ffb@tu-berlin.de>
2023-05-09 12:27 ` question on contributing to the xdp project Magnus Karlsson
     [not found]   ` <3feb89faadcb449881f92dc690049076@tu-berlin.de>
2023-05-09 13:11     ` Magnus Karlsson [this message]

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

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

  git send-email \
    --in-reply-to=CAJ8uoz1pkOv0kJNKwOQtZ5-8boQKQ6J-ZyU01K4NdqRXj3k-eg@mail.gmail.com \
    --to=magnus.karlsson@gmail.com \
    --cc=b.le@tu-berlin.de \
    --cc=bjorn.topel@gmail.com \
    --cc=magnus.karlsson@intel.com \
    --cc=xdp-newbies@vger.kernel.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).