DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Dey, Souvik" <sodey@sonusnet.com>
Cc: dev@dpdk.org, "Patil, PraveenKumar" <ppatil@sonusnet.com>
Subject: Re: [dpdk-dev] FW: BUG in IP FRAGMENTATION
Date: Wed, 15 Oct 2014 13:23:43 +0200	[thread overview]
Message-ID: <471124659.68G021lYDz@xps13> (raw)
In-Reply-To: <4B8F36DD0FB25E47B3DA6F493BF591B70DC5972B@inba-mail02.sonusnet.com>

ME TOO, I HAVE A BUG WITH CAPS LOCK ;)

2014-10-15 11:06, Dey, Souvik:
> In DPDK1.6 do we support overlapped fragments while doing reassembly.
> Also why we don't consider the first or last fragment to be out-of-order.
> Are this known limitations in DPDK or they are not working due to some
> bugs in the code ?

Please test the latest version and explain how you see the bug.

Thanks
-- 
Thomas

  reply	other threads:[~2014-10-15 11:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 11:06 Dey, Souvik
2014-10-15 11:23 ` Thomas Monjalon [this message]
2014-10-15 11:52   ` Dey, Souvik
2014-10-15 12:18     ` Ananyev, Konstantin
2014-10-15 12:30       ` Dey, Souvik

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=471124659.68G021lYDz@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ppatil@sonusnet.com \
    --cc=sodey@sonusnet.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).