DPDK usage discussions
 help / color / mirror / Atom feed
From: 芦翔 <luxiang@anweitech.com>
To: "users" <users@dpdk.org>
Cc: 许宝东 <xubaodong@anweitech.com>, 郑彤 <zhengtong@anweitech.com>
Subject: DPDK 22.11 - Question for TCP data processing
Date: Thu, 08 Jun 2023 01:55:05 +0800	[thread overview]
Message-ID: <52e41412-ce40-4407-96ef-13b1a39098a8.luxiang@anweitech.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]

Hello All,
I am a newbie here. I am working on a link layer device to fit for a special scenario, which is as follows:
Host 1 --- My Device --- Host2
At the very beginning, Host 1 and Host 2 are TCP connected. In this case, my device are introduced in the link between Host 1 and Host 2. What I have to do can be summarized as three folds:
(1) My device should be a link layer device to work without any affects for Host 1 and Host 2, in that case, no device in Host 1 and Host 2 needs to change current configurations, which are really not easy in my scenario. Host 1 and Host 2 can communicate with each other just like no my device are involved.
(2)Host 1 and Host 2 are out of my control, no product provider will support me to change even a character.
(3)My device should sign application layer payload and put signing values back to the application data, which are then encapsulated back to the TCP packet stream.
We are not sure that, how can we process those changed TCP packets to deal with various retransmissions like out-of-order, packet loss and so on. I am also review the previous threads in this mailing list. But as a newbie, I am not sure if I should turn to F-stack, KNI for the help from the protocol stack, or program a state checking applications in DPDK to calculate TCP sequence number and cache previous data for possible retransmission by myself. Or you may have better solution suggestions for us.
We are really appreciate your kind response.
Thank you and have a nice day.
Xiang

[-- Attachment #2: Type: text/html, Size: 2704 bytes --]

             reply	other threads:[~2023-06-07 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 17:55 芦翔 [this message]
2023-06-08  5:58 ` Pavel Vazharov

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=52e41412-ce40-4407-96ef-13b1a39098a8.luxiang@anweitech.com \
    --to=luxiang@anweitech.com \
    --cc=users@dpdk.org \
    --cc=xubaodong@anweitech.com \
    --cc=zhengtong@anweitech.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).