From: Thomas Monjalon <thomas@monjalon.net>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: dev@dpdk.org, 'Jerin Jacob' <jerin.jacob@caviumnetworks.com>,
"Wiles, Keith" <keith.wiles@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] Service lcores and Application lcores
Date: Thu, 29 Jun 2017 22:18:44 +0200 [thread overview]
Message-ID: <25008072.aWAPEDBPgL@xps> (raw)
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA640C33FD9@IRSMSX102.ger.corp.intel.com>
29/06/2017 18:35, Van Haaren, Harry:
> 3) The problem;
> If a service core runs the SW PMD schedule() function (option 2) *AND*
> the application lcore runs schedule() func (option 1), the result is that
> two threads are concurrently running a multi-thread unsafe function.
Which function is multi-thread unsafe?
Why the same function would be run by the service and by the scheduler?
next prev parent reply other threads:[~2017-06-29 20:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 14:36 Van Haaren, Harry
2017-06-29 15:16 ` Thomas Monjalon
2017-06-29 16:35 ` Van Haaren, Harry
2017-06-29 20:18 ` Thomas Monjalon [this message]
2017-06-30 8:52 ` Van Haaren, Harry
2017-06-30 9:29 ` Thomas Monjalon
2017-06-30 10:18 ` Van Haaren, Harry
2017-06-30 10:38 ` Thomas Monjalon
2017-06-30 11:14 ` Van Haaren, Harry
2017-06-30 13:04 ` Jerin Jacob
2017-06-30 13:16 ` Van Haaren, Harry
2017-06-29 15:57 ` Bruce Richardson
2017-06-30 4:45 ` Jerin Jacob
2017-06-30 10:00 ` Van Haaren, Harry
2017-06-30 12:51 ` Jerin Jacob
2017-06-30 13:08 ` Van Haaren, Harry
2017-06-30 13:20 ` Jerin Jacob
2017-06-30 13:24 ` Van Haaren, Harry
2017-06-30 13:51 ` Thomas Monjalon
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=25008072.aWAPEDBPgL@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=keith.wiles@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).