From: Thomas Monjalon <thomas@monjalon.net>
To: dave@barachs.net
Cc: "'Mattias Rönnblom'" <mattias.ronnblom@ericsson.com>,
"'Jerin Jacob'" <jerinjacobk@gmail.com>,
"'Jerin Jacob'" <jerinj@marvell.com>,
"'Ray Kinsella'" <mdr@ashroe.eu>, 'dpdk-dev' <dev@dpdk.org>,
"'Prasun Kapoor'" <pkapoor@marvell.com>,
"'Nithin Dabilpuram'" <ndabilpuram@marvell.com>,
"'Kiran Kumar K'" <kirankumark@marvell.com>,
"'Pavan Nikhilesh'" <pbhagavatula@marvell.com>,
"'Narayana Prasad'" <pathreya@marvell.com>,
nsaxena@marvell.com, sshankarnara@marvell.com,
"'Honnappa Nagarahalli'" <honnappa.nagarahalli@arm.com>,
"'David Marchand'" <david.marchand@redhat.com>,
"'Ferruh Yigit'" <ferruh.yigit@intel.com>,
"'Andrew Rybchenko'" <arybchenko@solarflare.com>,
"'Ajit Khaparde'" <ajit.khaparde@broadcom.com>,
"'Ye, Xiaolong'" <xiaolong.ye@intel.com>,
"'Raslan Darawsheh'" <rasland@mellanox.com>,
"'Maxime Coquelin'" <maxime.coquelin@redhat.com>,
"'Akhil Goyal'" <akhil.goyal@nxp.com>,
"'Cristian Dumitrescu'" <cristian.dumitrescu@intel.com>,
"'John McNamara'" <john.mcnamara@intel.com>,
"'Richardson, Bruce'" <bruce.richardson@intel.com>,
"'Anatoly Burakov'" <anatoly.burakov@intel.com>,
"'Gavin Hu'" <gavin.hu@arm.com>,
"'David Christensen'" <drc@linux.vnet.ibm.com>,
"'Ananyev, Konstantin'" <konstantin.ananyev@intel.com>,
"'Pallavi Kadam'" <pallavi.kadam@intel.com>,
"'Olivier Matz'" <olivier.matz@6wind.com>,
"'Gage Eads'" <gage.eads@intel.com>,
"'Rao, Nikhil'" <nikhil.rao@intel.com>,
"'Erik Gabriel Carrillo'" <erik.g.carrillo@intel.com>,
"'Hemant Agrawal'" <hemant.agrawal@nxp.com>,
"'Artem V. Andreev'" <artem.andreev@oktetlabs.ru>,
"'Stephen Hemminger'" <sthemmin@microsoft.com>,
"'Shahaf Shuler'" <shahafs@mellanox.com>,
"'Wiles, Keith'" <keith.wiles@intel.com>,
"'Jasvinder Singh'" <jasvinder.singh@intel.com>,
"'Vladimir Medvedkin'" <vladimir.medvedkin@intel.com>,
techboard@dpdk.org,
"'Stephen Hemminger'" <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [RFC PATCH 0/5] graph: introduce graph subsystem
Date: Fri, 21 Feb 2020 17:04:00 +0100 [thread overview]
Message-ID: <3455881.MHq7AAxBmi@xps> (raw)
In-Reply-To: <001d01d5e8cf$0bd6abb0$23840310$@barachs.net>
21/02/2020 16:53, dave@barachs.net:
> I can share a data-point with respect to constructing a reasonably functional network stack. Original work on the project which eventually became fd.io vpp started in 2002. I've worked on the vpp code base full-time for 18 years.
>
> In terms of lines of code: the vpp graph subsystem is a minuscule fraction of the project as a whole. We've rewritten performance-critical bits of the vpp netstack multiple times.
Please could you elaborate?
It would be nice to read more about your thoughts and experience.
next prev parent reply other threads:[~2020-02-21 16:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 17:01 jerinj
2020-01-31 17:01 ` [dpdk-dev] [RFC PATCH 1/5] " jerinj
2020-02-02 10:34 ` Stephen Hemminger
2020-02-02 10:35 ` Stephen Hemminger
2020-02-02 11:08 ` Jerin Jacob
2020-02-02 10:38 ` Stephen Hemminger
2020-02-02 11:21 ` Jerin Jacob
2020-02-03 9:14 ` Gaetan Rivet
2020-02-03 9:49 ` Jerin Jacob
2020-01-31 17:01 ` [dpdk-dev] [RFC PATCH 2/5] node: add packet processing nodes jerinj
2020-01-31 17:01 ` [dpdk-dev] [RFC PATCH 3/5] test: add graph functional tests jerinj
2020-01-31 17:02 ` [dpdk-dev] [RFC PATCH 4/5] test: add graph performance test cases jerinj
2020-01-31 17:02 ` [dpdk-dev] [RFC PATCH 5/5] example/l3fwd_graph: l3fwd using graph architecture jerinj
2020-01-31 18:34 ` [dpdk-dev] [RFC PATCH 0/5] graph: introduce graph subsystem Ray Kinsella
2020-02-01 5:44 ` Jerin Jacob
2020-02-17 7:19 ` Jerin Jacob
2020-02-17 8:38 ` Thomas Monjalon
2020-02-17 10:58 ` Jerin Jacob
2020-02-21 10:30 ` Jerin Jacob
2020-02-21 11:10 ` Thomas Monjalon
2020-02-21 15:38 ` Mattias Rönnblom
2020-02-21 15:53 ` dave
2020-02-21 16:04 ` Thomas Monjalon [this message]
2020-02-21 15:56 ` Jerin Jacob
2020-02-21 16:14 ` Thomas Monjalon
2020-02-22 9:05 ` Jerin Jacob
2020-02-22 9:52 ` Thomas Monjalon
2020-02-22 10:24 ` Jerin Jacob
2020-02-24 10:59 ` Ray Kinsella
2020-02-25 5:22 ` Honnappa Nagarahalli
2020-02-25 6:14 ` Jerin Jacob
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=3455881.MHq7AAxBmi@xps \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=akhil.goyal@nxp.com \
--cc=anatoly.burakov@intel.com \
--cc=artem.andreev@oktetlabs.ru \
--cc=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dave@barachs.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=erik.g.carrillo@intel.com \
--cc=ferruh.yigit@intel.com \
--cc=gage.eads@intel.com \
--cc=gavin.hu@arm.com \
--cc=hemant.agrawal@nxp.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jasvinder.singh@intel.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=john.mcnamara@intel.com \
--cc=keith.wiles@intel.com \
--cc=kirankumark@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=maxime.coquelin@redhat.com \
--cc=mdr@ashroe.eu \
--cc=ndabilpuram@marvell.com \
--cc=nikhil.rao@intel.com \
--cc=nsaxena@marvell.com \
--cc=olivier.matz@6wind.com \
--cc=pallavi.kadam@intel.com \
--cc=pathreya@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=pkapoor@marvell.com \
--cc=rasland@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=sshankarnara@marvell.com \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.com \
--cc=techboard@dpdk.org \
--cc=vladimir.medvedkin@intel.com \
--cc=xiaolong.ye@intel.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).