mtcp | Highly Scalable User-level TCP Stack | TCP library

by vpp-dev C Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | mtcp Summary

mtcp is a C library typically used in Networking, TCP, Docker applications. mtcp has no bugs, it has no vulnerabilities and it has low support. However mtcp has a Non-SPDX License. You can download it from GitHub.

mtcp is a highly scalable user-level tcp stack for multicore systems. mtcp source code is distributed under the modified bsd license. for more detail, please refer to the license. the license term of io_engine driver and ported applications may differ from the mtcp’s. we require the following libraries to run mtcp. - libps (packetshader i/o engine library) or libdpdk (intel’s dpdk package*) - libnuma - libpthread - librt compling psio/dpdk driver requires kernel headers. - for debian/ubuntu, try apt-get install linux-headers-$(uname -r). mtcp - mtcp source code directory mtcp/src - source code mtcp/src/include - mtcp’s internal header files mtcp/lib - library file mtcp/include - header files that applications will use. io_engine - event-driven packet i/o

Support

Quality

Security

License

Reuse

Support

mtcp has a low active ecosystem.

It has 5 star(s) with 1 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

mtcp has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of mtcp is current.

Quality

mtcp has 0 bugs and 0 code smells.

Security

mtcp has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

mtcp code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

mtcp has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

mtcp releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

It has 4782 lines of code, 61 functions and 64 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of mtcp

Get all kandi verified functions for this library.

mtcp Key Features

No Key Features are available at this moment for mtcp.

mtcp Examples and Code Snippets

No Code Snippets are available at this moment for mtcp.

Community Discussions

Trending Discussions on mtcp

Does DPDK provide a native TCP/IP network stack implemetation?

container is not able to access other container port

QUESTION

Does DPDK provide a native TCP/IP network stack implemetation?

Asked 2021-Jan-24 at 04:17

I'm trying to find out if there is any native TCP/IP stack implemetation provided in DPDK or any popular open-source project to achieve it. Any help will be grateful.

Update: My platform is Ubuntu 16.04 x64, Intel 82599es NIC with DPDK 20.08. What I'm trying to accomplish is to rebuild TCP connections out of the packets I receive on the NIC port for later use. I thought tools like ANS, mTCP and fstack may do the track but they are third party and some of them are not fully open-sourced, so I'm looking for a native one or one that is popular for developers. I don't know what should I call this kind of requirement, sorry for troubles causing because of the question, I'll change it after I know the related concept better.

...

ANSWER

Answered 2021-Jan-24 at 04:17

There are no native TCP-IP stack implementation in DPDK version till date DPDK version 20.11 LTS. Going further in my humble opinion DPDK would not be implementing native TCP-IP stack. Hence current options are

Since the requirement is to rebuild TCP connection state information, my recommendation is to

create RTE_FLOW_ACTION_MIRROR to create the packet copy at HW NIC level for all interested TCP connection using a combination of IP-TCP address-ports.
If there is no HW option, either using ref_cnt_update or copying the user packet payload create a copy of the packet.
With help RTE_RINGS or RTE_FB_ARRAY organize the packets from client and server based on symmetric RSS (if available) or based on custom HASH to appropriate containers.
For you packet processing recommendation is either use FSTACK or mTCP or BSD TCP-ip from scratch

there are multiple references on the Internet which gives hints to get started too. Please refer

mTCP slide 14
fstack slide deck

Source https://stackoverflow.com/questions/65841190

QUESTION

container is not able to access other container port

Asked 2020-Feb-05 at 09:12

I have a container that runs jupyter-hub on 443 and mapped to 1443 on the host. I'm trying to run this server behind the apache in another container. But, the two containers are not able to talk to each other.

I have tried setting the iptables for each container, but no use.

...

ANSWER

Answered 2020-Feb-05 at 09:12

The problem when the 2 containers not able to talk to each other is due to the fact that they are not in the same docker network. Here are what you have to do:

List all the available networks: docker network ls
Find out which network the apache container is running in

Source https://stackoverflow.com/questions/60071510

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install mtcp

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: