DPDK patches and discussions
 help / color / mirror / Atom feed
From: Mukesh Dua <mukesh.dua81@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Issue observed with execution of Reorder test app
Date: Thu, 20 Aug 2015 17:08:56 +0530	[thread overview]
Message-ID: <CAF0OvsZ0n-yTvx_-YF79ugyz4kmsOm9cLopuHY6PHpKRne=xEg@mail.gmail.com> (raw)

I see issue with reorder test app failing on x86 environment due to changes
made between release 2.0.0 and 2.1.0:

App reorder_test (app/test/test_reorder.c)
============
Function failing: test_reorder_insert

There had been some changes with respect to addition of parameter
is_initialized to the structure rte_reorder_buffer. In parallel the changes
were made to initialize some of the parameters in function
rte_reorder_insert

rte_reorder_insert(struct rte_reorder_buffer *b, struct rte_mbuf *mbuf)
{
    uint32_t offset, position;
    struct cir_buffer *order_buf = &b->order_buf;

*    if (!b->is_initialized) {*
*        b->min_seqn = mbuf->seqn;*
        *b->is_initialized = 1;*
*    }*

=> I don't see any reason to set b->min_seqn to mbuf->seqn and if that has
to be done, the conditional checks should have been modified in function
test_reorder_insert soon after a call to rte_reorder_insert. Additionally,
the next seqn number being populated should have been changed in function
test_reorder_insert:

    ret = rte_reorder_insert(b, bufs[0]);
*    if (!((ret == -1) && (rte_errno == ERANGE))) {*
*        printf("%s:%d: No error inserting late packet with seqn:"*
*                " 3 * size\n", __func__, __LINE__);*
*        ret = -1;*
*        goto exit;*
*    }*

    for (i = 0; i < num_bufs; i++)
        bufs[i]->seqn = i;

On the other hand, changing the code in function rte_reorder_insert:
rte_reorder_insert(struct rte_reorder_buffer *b, struct rte_mbuf *mbuf)
{
    uint32_t offset, position;
    struct cir_buffer *order_buf = &b->order_buf;

    if (!b->is_initialized) {
*        b->min_seqn = 0;  //Removed initialization from mbuf->seqn*
        b->is_initialized = 1;
    }
fixes the issues and the test case passes.

Regards,
Mukesh

             reply	other threads:[~2015-08-20 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 11:38 Mukesh Dua [this message]
2015-08-20 12:05 ` Gonzalez Monroy, Sergio
2015-08-20 17:36   ` Mukesh Dua

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='CAF0OvsZ0n-yTvx_-YF79ugyz4kmsOm9cLopuHY6PHpKRne=xEg@mail.gmail.com' \
    --to=mukesh.dua81@gmail.com \
    --cc=dev@dpdk.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).