From: David Marchand <david.marchand@redhat.com>
To: "Ruifeng Wang (Arm Technology China)" <Ruifeng.Wang@arm.com>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"Kantecki, Tomasz" <tomasz.kantecki@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] add lock-free mode for l3fwd
Date: Wed, 6 Nov 2019 15:03:54 +0100 [thread overview]
Message-ID: <CAJFAV8xaf9=azJiakvxZTjOiLVj-eWc8JSBY4tgibnF3XiOOsg@mail.gmail.com> (raw)
In-Reply-To: <AM0PR08MB39868D5510C50F1313213CD79E8C0@AM0PR08MB3986.eurprd08.prod.outlook.com>
Hello Ruifeng,
On Mon, Sep 16, 2019 at 4:30 AM Ruifeng Wang (Arm Technology China)
<Ruifeng.Wang@arm.com> wrote:
> > Not sure why it has to be master core?
> > Why interrupt thread wouldn't do?
> > I think what we need to:
> > 1. introduce reading routes from config file instead of having them hard-
> > coded within the app.
> > 2. add ability to update routes dynamically.
> > Probably the easiest (and commonly used way) re-read conf file and
> > update routes on the signal (SIGUSR1 or so).
> > Konstantin
> >
> >
> Sorry for delayed response. Just back from vacation.
> Thanks for your suggestion.
> I will try the config file based updating approach and get back with new version.
Any update on this series?
--
David Marchand
next prev parent reply other threads:[~2019-11-06 14:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 10:26 Ruifeng Wang
2019-09-06 10:26 ` [dpdk-dev] [PATCH 1/2] examples/l3fwd: add lock-free option " Ruifeng Wang
2019-09-06 10:26 ` [dpdk-dev] [PATCH 2/2] examples/l3fwd: integrate RCU QSBR for LPM mode Ruifeng Wang
2019-09-06 10:35 ` [dpdk-dev] [PATCH 0/2] add lock-free mode for l3fwd Ananyev, Konstantin
2019-09-09 1:52 ` Ruifeng Wang (Arm Technology China)
2019-09-09 22:45 ` Honnappa Nagarahalli
2019-09-10 6:25 ` Ruifeng Wang (Arm Technology China)
2019-09-11 5:32 ` Honnappa Nagarahalli
2019-09-11 6:18 ` Ruifeng Wang (Arm Technology China)
2019-09-10 9:06 ` Ananyev, Konstantin
2019-09-10 9:56 ` Ruifeng Wang (Arm Technology China)
2019-09-11 5:38 ` Honnappa Nagarahalli
2019-09-11 6:58 ` Ruifeng Wang (Arm Technology China)
2019-09-11 8:35 ` Ananyev, Konstantin
2019-09-16 2:30 ` Ruifeng Wang (Arm Technology China)
2019-11-06 14:03 ` David Marchand [this message]
2019-11-11 5:19 ` Ruifeng Wang (Arm Technology China)
2019-09-06 17:28 ` Stephen Hemminger
2019-09-09 2:38 ` Ruifeng Wang (Arm Technology China)
2019-09-10 16:27 ` Honnappa Nagarahalli
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='CAJFAV8xaf9=azJiakvxZTjOiLVj-eWc8JSBY4tgibnF3XiOOsg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=Gavin.Hu@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=tomasz.kantecki@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).