DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v8] eal: make lcore_config private
Date: Tue, 22 Oct 2019 18:49:02 +0200	[thread overview]
Message-ID: <CAJFAV8yzX7CLHkE3UG32viqrhb9-5x9oC6Oc+G6Ln0KipLGxRw@mail.gmail.com> (raw)
In-Reply-To: <20191022093045.3d02805a@hermes.lan>

On Tue, Oct 22, 2019 at 6:30 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> On Tue, 22 Oct 2019 11:05:01 +0200
> David Marchand <david.marchand@redhat.com> wrote:
>
> > On Wed, Oct 2, 2019 at 9:40 PM Stephen Hemminger
> > <stephen@networkplumber.org> wrote:
> > > +struct lcore_config {
> > > +       pthread_t thread_id;       /**< pthread identifier */
> > > +       int pipe_master2slave[2];  /**< communication pipe with master */
> > > +       int pipe_slave2master[2];  /**< communication pipe with master */
> > > +
> > > +       lcore_function_t * volatile f; /**< function to call */
> > > +       void * volatile arg;       /**< argument of function */
> > > +       volatile int ret;          /**< return value of function */
> > > +
> > > +       uint32_t core_id;          /**< core number on socket for this lcore */
> > > +       uint32_t core_index;       /**< relative index, starting from 0 */
> > > +       uint16_t socket_id;        /**< physical socket id for this lcore */
> > > +       uint8_t core_role;         /**< role of core eg: OFF, RTE, SERVICE */
> > > +       uint8_t detected;          /**< true if lcore was detected */
> > > +       volatile enum rte_lcore_state_t state; /**< lcore state */
> > > +       rte_cpuset_t cpuset;       /**< cpu set which the lcore affinity to */
> > > +};
> >
> > There are still changes on the core_id, core_index, socket_id that I
> > am not confortable with (at this point).
> >
> > I prepared a series for -rc1 on ABI changes in EAL (that I will send shortly).
> > I took your patch without the changes on core_id, core_index and socket_id.
>
>
> Why, please be more precise.
>

I commented earlier that there were integer conversion with the fields
you changed.

core_id is ok, and a uint32_t would be fine, but this does not change the size.
socket_id needs investigation, but should be safe.
I am nervous about core_index, because it is used as a signed integer.

It looks too dangerous to blindly accept this change with the only
reason of saving space.


-- 
David Marchand


      reply	other threads:[~2019-10-22 16:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 16:10 [dpdk-dev] [PATCH v7] " Stephen Hemminger
2019-10-02  8:15 ` David Marchand
2019-10-02 19:40 ` [dpdk-dev] [PATCH v8] " Stephen Hemminger
2019-10-22  9:05   ` David Marchand
2019-10-22 16:30     ` Stephen Hemminger
2019-10-22 16:49       ` David Marchand [this message]

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=CAJFAV8yzX7CLHkE3UG32viqrhb9-5x9oC6Oc+G6Ln0KipLGxRw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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).