From: Suraj R Gupta <surajrgupta@iith.ac.in>
To: dev@dpdk.org
Cc: users@dpdk.org
Subject: Re: [dpdk-users] [dpdk-dev] Issue in draining packets when head is null
Date: Thu, 23 Jan 2020 23:23:37 +0530 [thread overview]
Message-ID: <CAMfGv3=XzwYGk6dTn9xcb2uNs5yxeQrrjTtjgse+X26JoBdjQQ@mail.gmail.com> (raw)
In-Reply-To: <CAMfGv3=AtM+rqrhVRRH3wfiJskvrcp4ikB+B9S+=UrAq8A2n8A@mail.gmail.com>
Folks,
Any Ideas on this.
On Mon, Jan 13, 2020 at 1:04 PM Suraj R Gupta <surajrgupta@iith.ac.in>
wrote:
> Hi all,
> This is regarding an issue in the draining packet using rte_reorder_drain.
> Suppose we have a window size of 16 and we get packets with sequence no
> like 0,1,2,4,5,6. On performing drain operation, I retrieve packets like
> 0,1,2.
> Since now order_buf->entries[order_buf->head] i.e. order_buf->entries[3]
> is null i won't be able to any more like 4,5,6. I would be able to do it
> only when I get at a packet with a sequence number above window size. This
> may be highly undesirable if we have large window sizes say 1024, 2048,
> etc. we wouldn't be able to drain any more packets until a packet above
> window size is received. Also since the struct rte_rorder_buffer are
> defined in the source .c file, we are not able to move head of buffer from
> applications. *Is there any specific reasons why it is implemented like
> this in the library. Are there any ways to overcome this.*
> --
> Thanks and Regards
> Suraj R Gupta
>
--
Thanks and Regards
Suraj R Gupta
next prev parent reply other threads:[~2020-01-23 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 7:34 Suraj R Gupta
2020-01-23 17:53 ` Suraj R Gupta [this message]
2020-01-23 18:23 ` Muhammad Zain-ul-Abideen
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='CAMfGv3=XzwYGk6dTn9xcb2uNs5yxeQrrjTtjgse+X26JoBdjQQ@mail.gmail.com' \
--to=surajrgupta@iith.ac.in \
--cc=dev@dpdk.org \
--cc=users@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).