From: Sam Kirubakaran <samkirubakaranl@gmail.com>
To: Liang Ma <liangma@liangbit.com>
Cc: dev@dpdk.org
Subject: Re: TCP stack support on DPDK
Date: Tue, 24 Jan 2023 13:24:38 +0530 [thread overview]
Message-ID: <CAAmbQF_dv4bcSuDvrVVFFA_rB6RO2-9F6s+NLsfkqU4oFJ2+hA@mail.gmail.com> (raw)
In-Reply-To: <Y85fBu546ot2RI1Y@C02GF04TMD6V>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
Hi Liang,
Thank you so much for your response.
I would like to convert our in-house tool into a high performance traffic
generator and it is written in Python.
Is it possible to use any of the user space TCP stack by compiling into
shared libraries and access it via Python using ctypes?
Could you please let me know any viable solution to make use of user space
TCP stack compatible with Python?
Regards,
Sam
On Mon, Jan 23, 2023 at 3:48 PM Liang Ma <liangma@liangbit.com> wrote:
> On Fri, Jan 20, 2023 at 01:41:56PM +0530, Sam Kirubakaran wrote:
> > Hi team,
> >
> > My name is Sam and I am a Software Engineer.
> > Currently, we are trying to improve the performance of proprietary
> in-house
> > tools by using DPDK but we are not sure whether DPDK has support for TCP
> > stack.
> > If yes, could you please point me to the link of apis alone. I will take
> it
> > from there.
> > Could you please guide me on this? Your response would be highly
> > appreciated!
> DPDK itself has no TCP stack. However, there are some userspace TCP
> stack project which support DPDK. TPDK/Seastar/fullstack etc.
> >
> > Regards,
> > Sam
>
[-- Attachment #2: Type: text/html, Size: 1589 bytes --]
next prev parent reply other threads:[~2023-01-25 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 8:11 Sam Kirubakaran
2023-01-20 11:31 ` Thomas Monjalon
2023-01-20 16:51 ` Sam Kirubakaran
2023-01-23 10:18 ` Liang Ma
2023-01-24 7:54 ` Sam Kirubakaran [this message]
2023-02-16 14:39 ` Liang Ma
2023-02-16 15:01 ` Van Haaren, Harry
2023-02-16 21:00 ` Liang Ma
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=CAAmbQF_dv4bcSuDvrVVFFA_rB6RO2-9F6s+NLsfkqU4oFJ2+hA@mail.gmail.com \
--to=samkirubakaranl@gmail.com \
--cc=dev@dpdk.org \
--cc=liangma@liangbit.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).