Using different TCP/IP stacks with separately allocated resources

Patent metadata

Field	Value
Publication number	US-10091125-B2
Application number	US-201414231707-A
Country	US
Kind code	B2
Filing date	Mar 31, 2014
Priority date	Mar 31, 2014
Publication date	Oct 2, 2018
Grant date	Oct 2, 2018

Abstract

Multiple TCP/IP stack processors on a host. The multiple TCP/IP stack processors are provided independently of TCP/IP stack processors implemented by virtual machines on the host. The TCP/IP stack processors provide multiple different default gateway addresses for use with multiple processes. The default gateway addresses allow a service to communicate across an L3 network. Processes outside of virtual machines that utilize the TCP/IP stack processor on a first host can benefit from using their own gateway, and communicate with their peer process on a second host, regardless of whether the second host is located within the same subnet or a different subnet. The multiple TCP/IP stack processors can use separately allocated resources. Separate TCP/IP stack processors can be provided for each of multiple tenants on the host. Separate loopback interfaces of multiple TCP/IP stack processors can be used to create separate containment for separate sets of processes on a host.

First claim

What is claimed is:

1. A method of implementing TCP/IP stacks on an electronic computing device that implements a plurality of TCP/IP stacks, the method comprising:
allocating a first amount of memory resources for a first TCP/IP stack for a first process executing on the device outside of any virtual machine;
allocating a second amount of memory resources for a second TCP/IP stack for a second process executing outside of any virtual machine, said second amount of resources separate from the first amount of memory resources;
implementing the first TCP/IP stack with the first amount of memory resources; and
implementing the second TCP/IP stack with the second amount of memory resources,
wherein memory resources allocated to a particular TCP/IP stack are not available for use by any other TCP/IP stack.

2. The method of claim 1 , wherein at least one of the first and second processes is a storage process.

3. The method of claim 2 , wherein the storage process is one of a network file system and a virtual storage area network.

4. The method of claim 1 , wherein the first process is a storage process and the second process is a virtual machine migration process.

5. The method of claim 1 , wherein the first amount of memory resources is determined by a configuration file of the first TCP/IP stack and the second amount of memory resources is determined by a configuration file of the second TCP/IP stack.

6. The method of claim 1 , wherein the first amount of memory resources is determined based on resource allocation requirements of a plurality of TCP/IP stacks.

7. The method of claim 6 , wherein the plurality of TCP/IP stacks comprises a plurality of presently implemented TCP/IP stacks.

8. The method of claim 6 , wherein the plurality of TCP/IP stacks comprises a plurality of presently implemented TCP/IP stacks and a plurality of presently unimplemented TCP/IP stacks with known resource allocation requirements.

9. The method of claim 1 , wherein said implementing the first and second TCP/IP stacks is performed by the electronic device automatically during a boot up of the electronic device.

10. A non-transitory machine readable medium storing a program which when executed by at least one processing unit implements a plurality of TCP/IP stacks, outside of any virtual machine, the program comprising sets of instructions for:
allocating a first amount of memory resources for a first TCP/IP stack for a first process executing on the device outside of any virtual machine; and
allocating a second amount of memory resources for a second TCP/IP stack for a second process executing outside of any virtual machine, said second amount of resources separate from the first amount of memory resources,
implementing the first TCP/IP stack with the first amount of memory resources; and
implementing the second TCP/IP stack with the second amount of memory resources,
wherein memory resources allocated to a particular TCP/IP stack are not available for use by any other TCP/IP stack.

11. The non-transitory machine readable medium of claim 10 , wherein the first and second processes are hypervisor service processes.

12. The non-transitory machine readable medium of claim 10 , the program further comprising a set of instructions for implementing connections with the first amount of memory resources and the second amount of memory resources.

13. The non-transitory machine readable medium of claim 10 , the program further comprising a set of instructions for implementing sockets with the first amount of memory resources and the second amount of memory resources.

14. The non-transitory machine readable medium of claim 10 , wherein the first amount of memory resources is equal to the second amount of memory resources.

15. The non-transitory machine readable medium of claim 10 , wherein the first amount of memory resources is different from the second amount of memory resources.

16. The non-transitory machine readable medium of claim 15 , wherein the first amount of memory resources is determined by a configuration file of the first TCP/IP stack and the second amount of memory resources is determined by a configuration file of the second TCP/IP stack.

17. The non-transitory machine readable medium of claim 15 , wherein the first amount of memory resources is determined based on resource allocation requirements of a plurality of TCP/IP stacks.

18. An electronic device implementing a first service and a second service, the electronic device comprising:
at least one processing unit; and
a non-transitory machine readable medium storing a program that when executed by the at least one processing units implements a plurality of TCP/IP stacks outside of any virtual machine on the electronic device, the program comprising sets of instructions for:
allocating a first amount of memory resources to a first TCP/IP stack executing outside of any virtual machine to process data from the first service into IP packets;
allocating a second amount of memory resources separate from the first amount of memory resources to a second TCP/IP stack outside of any virtual machine to process data from the second service into IP packets;
implementing the first TCP/IP stack with the first amount of resources to prevent data output operations of the first service from impacting the second amount of resources; and
implementing the second TCP/IP stack with the second amount of resources to prevent data operations of the second service from impacting the first amount of resources.

19. The electronic device of claim 18 , wherein the first amount of memory resources comprises a first memory space and the second amount of memory resources comprises a second memory space separate from the first memory space.

20. The electronic device of claim 18 , the program further comprising sets of instructions for implementing connections and sockets with the first amount of memory resources and the second amount of memory resources.

21. The electronic device of claim 18 , wherein the first service and the second service run on a kernel space on the electronic device.

Assignees

• Nicira Inc

Inventors

• Raju Nithin B
• Chandrashekhar Ganesan
• Pillai Gopakumar

Classifications

• G06F9/45533 Primary

  Hypervisors; Virtual machine monitors · CPC title

• H04L47/70 Primary

  Admission control; Resource allocation · CPC title