From: Jerin Jacob <jerinjacobk@gmail.com>
To: Robin Jarry <rjarry@redhat.com>
Cc: dev@dpdk.org, Jerin Jacob <jerinj@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [RFC] graph/node: feedback and future improvements
Date: Thu, 9 May 2024 13:54:59 +0530 [thread overview]
Message-ID: <CALBAE1NCtfLLkmds5V6sCYatcxhT36iTEu7Ow277T1mZmpE6Bg@mail.gmail.com> (raw)
In-Reply-To: <D14LQRP9WMDY.1NTP0R2BMTDNL@redhat.com>
On Thu, May 9, 2024 at 3:34 AM Robin Jarry <rjarry@redhat.com> wrote:
>
> Hi Jerin,
>
> Jerin Jacob, May 04, 2024 at 12:03:
> > 2) Control plane code: IMO, if you are willing, I will be glad to see
> > it is hosted at https://www.dpdk.org/hosted-projects/ like pktgen.
> > This may attract more developers for control plane code for
> > brouter and show good reference of using DPDK graph library.
> > I think, TB needs to approve for this. If you are OK, We can add
> > this to one of TB meeting agenda.
>
> Wow, thanks for suggesting this! Of course, I would be thrilled to have
> the project hosted in the DPDK namespace. Do I need to make a formal
> request to techboard@dpdk.org or is it premature?
IMO, If basic use case is running then you may request TB for approval
to host it.
>
> Thanks again!
>
next prev parent reply other threads:[~2024-05-09 8:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 14:17 Robin Jarry
2024-04-05 23:11 ` Jerin Jacob
2024-04-14 10:35 ` Robin Jarry
2024-04-24 13:24 ` Robin Jarry
2024-05-04 10:03 ` Jerin Jacob
2024-05-08 22:04 ` Robin Jarry
2024-05-09 8:24 ` Jerin Jacob [this message]
2024-05-15 8:10 ` Robin Jarry
2024-05-15 9:02 ` Bruce Richardson
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=CALBAE1NCtfLLkmds5V6sCYatcxhT36iTEu7Ow277T1mZmpE6Bg@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=rjarry@redhat.com \
--cc=thomas@monjalon.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;
as well as URLs for NNTP newsgroup(s).