From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Marohn, Byron" <byron.marohn@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH] test: reduce test duration for efd autotest
Date: Wed, 17 Oct 2018 14:34:12 +0000 [thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A3B9964@irsmsx110.ger.corp.intel.com> (raw)
In-Reply-To: <1537971540-31443-1-git-send-email-jananeex.m.parthasarathy@intel.com>
> -----Original Message-----
> From: Parthasarathy, JananeeX M
> Sent: Wednesday, September 26, 2018 3:19 PM
> To: dev@dpdk.org
> Cc: Marohn, Byron <byron.marohn@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; Pattan, Reshma
> <reshma.pattan@intel.com>; Parthasarathy, JananeeX M
> <jananeex.m.parthasarathy@intel.com>
> Subject: [PATCH] test: reduce test duration for efd autotest
>
> + uint8_t simple_key;
Following to my comments in my earlier mail,
Can this be uint64_t simple-key; ? so that we can retain simple_key to be of 64 bits as per original test case.
> efd_get_all_sockets_bitmask(),
> + sizeof(uint8_t),
sizeof(simple_key);
> + val = mrand48() & VALUE_BITMASK;
Having value here can make all has key entries to have same value.
But as per original test case, they want to have different value for each
hash key entry. So better move val update inside for loop itself.
> /* Add random entries until key cannot be added */
> for (added_keys = 0; added_keys < num_rules_in;
> added_keys++) {
>
> - for (i = 0; i < EFD_TEST_KEY_LEN; i++)
> - simple_key[i] = rte_rand() & 0xFF;
> + simple_key = rte_rand() & 0xFF;
If we agree to change simple_key to be of type unit64_t then masking with 0xFF will not be required here.
Instead of having val = mrand48() & VALUE_BITMASK; as above. Now you can do val = simple_key & 0xFF;
So for each key that is going to be updated we will have different value as per original test.
>
> - efd_value_t val = simple_key[0];
> -
> - if (rte_efd_update(handle, test_socket_id,
> simple_key,
> + if (rte_efd_update(handle, test_socket_id,
> &simple_key,
Thanks,
Reshma
next prev parent reply other threads:[~2018-10-17 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 14:19 Jananee Parthasarathy
2018-10-17 13:33 ` Pattan, Reshma
2018-10-17 14:34 ` Pattan, Reshma [this message]
2018-10-31 14:30 ` [dpdk-dev] [PATCH v2] " Jananee Parthasarathy
2018-10-31 16:11 ` Pattan, Reshma
2018-11-29 7:36 ` [dpdk-dev] [PATCH v3] " Jananee Parthasarathy
2019-01-20 21:25 ` Thomas Monjalon
2019-07-04 21:46 ` Thomas Monjalon
2019-07-19 9:01 ` Parthasarathy, JananeeX M
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=3AEA2BF9852C6F48A459DA490692831F2A3B9964@irsmsx110.ger.corp.intel.com \
--to=reshma.pattan@intel.com \
--cc=byron.marohn@intel.com \
--cc=dev@dpdk.org \
--cc=jananeex.m.parthasarathy@intel.com \
--cc=pablo.de.lara.guarch@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).