DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dekel Peled <dekelp@mellanox.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: Andrew Rybchenko <arybchenko@solarflare.com>,
	"wenzhuo.lu@intel.com" <wenzhuo.lu@intel.com>,
	"jingjing.wu@intel.com" <jingjing.wu@intel.com>,
	"bernard.iremonger@intel.com" <bernard.iremonger@intel.com>,
	Yongseok Koh <yskoh@mellanox.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>, Ori Kam <orika@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] ethdev: support action with any config object type
Date: Tue, 2 Jul 2019 10:17:01 +0000	[thread overview]
Message-ID: <AM4PR05MB34604D4221FF37FFDC4E6470B6F80@AM4PR05MB3460.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20190702095716.GA4512@6wind.com>

Thanks, PSB.

> -----Original Message-----
> From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
> Sent: Tuesday, July 2, 2019 12:57 PM
> To: Dekel Peled <dekelp@mellanox.com>
> Cc: Andrew Rybchenko <arybchenko@solarflare.com>;
> wenzhuo.lu@intel.com; jingjing.wu@intel.com;
> bernard.iremonger@intel.com; Yongseok Koh <yskoh@mellanox.com>;
> Shahaf Shuler <shahafs@mellanox.com>; Slava Ovsiienko
> <viacheslavo@mellanox.com>; dev@dpdk.org; Ori Kam
> <orika@mellanox.com>
> Subject: Re: [dpdk-dev] [PATCH] ethdev: support action with any config
> object type
> 
> On Tue, Jul 02, 2019 at 08:42:41AM +0000, Dekel Peled wrote:
> > Thanks, PSB.
> >
> > > -----Original Message-----
> > > From: Andrew Rybchenko <arybchenko@solarflare.com>
> > > Sent: Tuesday, July 2, 2019 11:09 AM
> > > To: Dekel Peled <dekelp@mellanox.com>; Adrien Mazarguil
> > > <adrien.mazarguil@6wind.com>; wenzhuo.lu@intel.com;
> > > jingjing.wu@intel.com; bernard.iremonger@intel.com; Yongseok Koh
> > > <yskoh@mellanox.com>; Shahaf Shuler <shahafs@mellanox.com>; Slava
> > > Ovsiienko <viacheslavo@mellanox.com>; arybchenko@solarflare.com
> > > Cc: dev@dpdk.org; Ori Kam <orika@mellanox.com>
> > > Subject: Re: [dpdk-dev] [PATCH] ethdev: support action with any
> > > config object type
> > >
> > > On 01.07.2019 17:10, Dekel Peled wrote:
> > > > In current implementation, an action which requires parameters
> > > > must accept them enclosed in a structure.
> > > > Some actions require a single, trivial type parameter, but it
> > > > still must be enclosed in a structure.
> > > > This obligation results in multiple, action-specific structures,
> > > > each containing a single trivial type parameter.
> > > >
> > > > This patch introduces a new approach, allowing an action
> > > > configuration object of any type, trivial or a structure.
> > > >
> > > > This patch introduces, in test-pmd, a new macro ARG_ENTRY_HTON, to
> > > > allow using a single argument, not enclosed in a structure.
> > > >
> > > > Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> > >
> > > The term "object" confuses me a bit, but I'm not a native speaker so
> > > it could be just my wrong association. I'd prefer "configuration data".
> >
> > In previous version I wrote just "action configuration", and changed to
> "action configuration object" per Adrien's suggestion. I think it is better, but if
> it causes confusion maybe it should be changed.
> >
> > Adrien, what do you think? Does "configuration data" carry the correct
> meaning?
> 
> Well I'm no native speaker either but "object" is the term used in the C
> standard with a well-defined meaning [1] and encompasses everything
> (integers, floats, structures, unions, functions, pointers, arrays):
> 
>  "region of data storage in the execution environment, the contents of which
>   can represent values"
> 
> I think it's a bit less vague than "data" because whenever objects are
> mentioned in the standard, they always have a type. There's no such thing as
> a C object without one, and rte_flow puts a lot of emphasis on documenting
> them.
> 
>  int foo;
>  struct { ... } foo;
>  double foo;
>  char foo[];
>  void *foo;
> 
> Whatever the type, would you refer to "foo" itself as an "object" or as
> "data"?

Understood, staying with "object".

> 
> Unrelated, but you must remove ARG_ENTRY_HTON from this patch since
> there's no testpmd change in there that requires it. There's no tolerance for
> dead code in testpmd as it doesn't expose an API.

OK, I'll remove it from this patch and add it to the relevant series.

> 
> Thanks.
> 
> [1] 3.14 "object"
> 
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.
> open-
> std.org%2Fjtc1%2Fsc22%2Fwg14%2Fwww%2Fdocs%2Fn1256.pdf&amp;data
> =02%7C01%7Cdekelp%40mellanox.com%7C305d2ae37a3b411ea91608d6fed3
> afbf%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C1%7C63697658247762
> 5253&amp;sdata=8wcANpiGcjbhVMFHWs1wRB%2FnkvoSOawmHm8bkavY2
> U4%3D&amp;reserved=0
> 
> --
> Adrien Mazarguil
> 6WIND

  parent reply	other threads:[~2019-07-02 10:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 14:10 Dekel Peled
2019-07-02  8:09 ` Andrew Rybchenko
2019-07-02  8:42   ` Dekel Peled
2019-07-02  9:57     ` Adrien Mazarguil
2019-07-02 10:11       ` Andrew Rybchenko
2019-07-02 10:15         ` Dekel Peled
2019-07-02 10:17       ` Dekel Peled [this message]
2019-07-02 14:17 ` [dpdk-dev] [PATCH v2] " Dekel Peled
2019-07-02 15:07   ` Andrew Rybchenko
2019-07-02 15:15   ` Adrien Mazarguil
2019-07-03 17:45     ` Ferruh Yigit

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=AM4PR05MB34604D4221FF37FFDC4E6470B6F80@AM4PR05MB3460.eurprd05.prod.outlook.com \
    --to=dekelp@mellanox.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=arybchenko@solarflare.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=orika@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=viacheslavo@mellanox.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=yskoh@mellanox.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).