Comments

• 

  almost 2 years ago by paolodepa | Reply

  Preliminary finding: as per https://doc.dpdk.org/guides/howto/virtiouserforcontainernetworking.html, two main configs seem to be supported: "Slicing" and "Aggregation". It's worth to try to setup both and compare their performances.

×
Edit Comment 7568
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Preliminary finding: as per https://doc.dpdk.org/guides/howto/virtio_user_for_container_networking.html, two main configs seem to be supported: "Slicing" and "Aggregation". It's worth to try to setup both and compare their performances.
 
×
Reply to paolodepa
Preliminary finding: as per https://doc.dpdk.org/guides/howto/virtiouserforcontainernetworking.html, two main configs seem to be supported: "Slicing" and "Aggregation". It's worth to try to setup both and compare their performances.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  almost 2 years ago by paolodepa | Reply

  Looking at https://doc.dpdk.org/guides/howto/virtiouserforcontainernetworking.html two main approaches emerge: slicing and aggregation. Slicing relies on SR-IOV and Virtual Functions: not having at hand an SR-IOV capable NIC I decided to postpone this investigation. Aggregation decouples the physical NIC access from the containers introducing OpenVSwitch as middle layer: this simplifies the setup and opens the door to connection between containers, VMs and VirtualApps.

  My investigation on how to connect containers using OVS is summarized here: https://github.com/paolo-depa/container-on-ovs

×
Edit Comment 7760
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Looking at https://doc.dpdk.org/guides/howto/virtio_user_for_container_networking.html two main approaches emerge: slicing and aggregation. Slicing relies on SR-IOV and Virtual Functions: not having at hand an SR-IOV capable NIC I decided to postpone this investigation. Aggregation decouples the physical NIC access from the containers introducing OpenVSwitch as middle layer: this simplifies the setup and opens the door to connection between containers, VMs and VirtualApps. My investigation on how to connect containers using OVS is summarized here: https://github.com/paolo-depa/container-on-ovs
 
×
Reply to paolodepa
Looking at https://doc.dpdk.org/guides/howto/virtiouserforcontainernetworking.html two main approaches emerge: slicing and aggregation. Slicing relies on SR-IOV and Virtual Functions: not having at hand an SR-IOV capable NIC I decided to postpone this investigation. Aggregation decouples the physical NIC access from the containers introducing OpenVSwitch as middle layer: this simplifies the setup and opens the door to connection between containers, VMs and VirtualApps.
My investigation on how to connect containers using OVS is summarized here: https://github.com/paolo-depa/container-on-ovs
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  almost 2 years ago by paolodepa | Reply

  Next steps: 1. Investigate Slicing scenario using the proper hardware; 2. Add a DPDK interface to an "Aggregation" bridge and benchmark north-south traffic; 3. Enter the kubernetes world...

×
Edit Comment 7763
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Next steps: 1. Investigate Slicing scenario using the proper hardware; 2. Add a DPDK interface to an "Aggregation" bridge and benchmark north-south traffic; 3. Enter the kubernetes world...
 
×
Reply to paolodepa
Next steps: 1. Investigate Slicing scenario using the proper hardware; 2. Add a DPDK interface to an "Aggregation" bridge and benchmark north-south traffic; 3. Enter the kubernetes world...
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview