DPDK patches and discussions
 help / color / mirror / Atom feed
From: Levend Sayar <levendsayar@gmail.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] acl: Fix RTE_ACL_RULE_SZ macro definition
Date: Tue, 7 Jul 2020 18:25:13 +0300	[thread overview]
Message-ID: <CAGDw98n+8HPor+ZXtidbZS1KZgcaDgfgraGFbVbiFXJThmWN3A@mail.gmail.com> (raw)
In-Reply-To: <BYAPR11MB330123DB9DB5F74EAC5A269E9A660@BYAPR11MB3301.namprd11.prod.outlook.com>

Sure.
I am really sorry for not being verbose enough.

From lib/librte_acl/rte_acl.h

#define RTE_ACL_RULE_DEF(name, fld_num) struct name {\
    struct rte_acl_rule_data data;               \
    struct rte_acl_field field[fld_num];         \
}

RTE_ACL_RULE_DEF(rte_acl_rule,);

When you put the definition in-place, above line means :

struct rte_acl_rule {
   struct rte_acl_rule_data data;
   struct rte_acl_field field[];
}

There is another define to get the size of an acl rule such as

#define RTE_ACL_RULE_SZ(fld_num)    \
    (sizeof(struct rte_acl_rule) + sizeof(struct rte_acl_field) * (fld_num))

So the above definition gets the size of a "struct rte_acl_rule" which has
fld_num fields.
which must be
*sizeof (struct rte_acl_rule_data) *+ (sizeof(struct rte_acl_field) *
fld_num)

Because it adds up the sizes of struct components;

But according to the current RTE_ACL_RULE_SZ, it is

*sizeof (struct rte_acl_rule)* + (sizeof(struct rte_acl_field) * fld_num)

So my patch only changes the part that I underlined.

sizeof (struct rte_acl_rule) = 16;
sizeof (struct rte_acl_rule_data) = 12;

Best,
Levend


On Tue, Jul 7, 2020 at 3:42 PM Ananyev, Konstantin <
konstantin.ananyev@intel.com> wrote:

>
> > From: Levend Sayar <levendsayar@gmail.com>
>
> Could you provide some explanation:
> What do you think is wrong with current version and why,
> and what your fix does.
>
> >
> > Signed-off-by: Levend Sayar <levendsayar@gmail.com>
> > ---
> >  lib/librte_acl/rte_acl.h | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/lib/librte_acl/rte_acl.h b/lib/librte_acl/rte_acl.h
> > index aa22e70c6..d34fdbc0e 100644
> > --- a/lib/librte_acl/rte_acl.h
> > +++ b/lib/librte_acl/rte_acl.h
> > @@ -116,7 +116,7 @@ struct rte_acl_rule_data {
> >  RTE_ACL_RULE_DEF(rte_acl_rule,);
> >
> >  #define      RTE_ACL_RULE_SZ(fld_num)        \
> > -     (sizeof(struct rte_acl_rule) + sizeof(struct rte_acl_field) *
> (fld_num))
> > +     (sizeof(struct rte_acl_rule_data) + sizeof(struct rte_acl_field) *
> (fld_num))
> >
> >
> >  /** Max number of characters in name.*/
> > --
> > 2.27.0
>
>

  reply	other threads:[~2020-07-08 12:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07 12:26 levendsayar
2020-07-07 12:42 ` Ananyev, Konstantin
2020-07-07 15:25   ` Levend Sayar [this message]
2020-07-07 16:44     ` Ananyev, Konstantin
2020-07-07 16:59       ` Levend Sayar

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=CAGDw98n+8HPor+ZXtidbZS1KZgcaDgfgraGFbVbiFXJThmWN3A@mail.gmail.com \
    --to=levendsayar@gmail.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@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).