DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Karuna Grewal <karunagrewal98@gmail.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, ajit.khaparde@broadcom.com
Subject: Re: [dpdk-dev] DPDK's GSoC participation
Date: Thu, 31 Jan 2019 18:49:34 +0100	[thread overview]
Message-ID: <6706445.jDfIes0TBL@xps> (raw)
In-Reply-To: <CAHRz_yb_3zStATz0RsYWyBtd9qxfio9pkpBh9E+A=ut-rU7Atw@mail.gmail.com>

31/01/2019 18:07, Karuna Grewal:
> Hi everyone,
> 
> I saw the previous thread about DPDK's GSoC ideas. As someone having
> experience using the same while investigating various userspace network
> stack implementations, I want to know if there are any beginner friendly
> tasks on bugzilla for me to start contributing to this project.
> Any pointers in this direction are appreciated.

That's a good question.
We should mark some easy tasks in bugzilla with a special priority.

Ferruh, Ajit, any comment?

  reply	other threads:[~2019-01-31 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 17:07 Karuna Grewal
2019-01-31 17:49 ` Thomas Monjalon [this message]
2019-02-01 17:00   ` Ferruh Yigit

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=6706445.jDfIes0TBL@xps \
    --to=thomas@monjalon.net \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=karunagrewal98@gmail.com \
    /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 NNTP newsgroup(s).