KTCPVS - Revision history

Wensong: /* Implementation */

2007-04-05T15:05:49Z

‎Implementation

Wensong at 03:41, 23 February 2007

2007-02-23T03:41:12Z

Wensong: /* Examples */

2007-02-23T03:39:37Z

‎Examples

Wensong at 15:54, 10 November 2006

2006-11-10T15:54:52Z

Wensong at 06:46, 2 October 2006

2006-10-02T06:46:16Z

Wensong at 03:57, 27 May 2006

2006-05-27T03:57:42Z

Wensong: /* Introduction */

2006-02-05T12:57:40Z

‎Introduction

Wensong at 12:53, 5 February 2006

2006-02-05T12:53:40Z

Wensong: /* Implementation */

2006-02-04T11:40:12Z

‎Implementation

Wensong at 03:37, 4 October 2005

2005-10-04T03:37:16Z

← Older revision		Revision as of 15:05, 5 April 2007
Line 25:		Line 25:

	In the KTCPVS, the [[kernel thread]]s are used to parse the content of requests, forward them to backend servers according to scheduling rules, and relay data between client and server. The user-space program tcpvsadm is to administrator KTCPVS, it can write the virtual server rules inside the kernel through setsockopt, and read the KTCPVS rules through getsockopt or /proc file system.		In the KTCPVS, the [[kernel thread]]s are used to parse the content of requests, forward them to backend servers according to scheduling rules, and relay data between client and server. The user-space program tcpvsadm is to administrator KTCPVS, it can write the virtual server rules inside the kernel through setsockopt, and read the KTCPVS rules through getsockopt or /proc file system.
		+
		+	In the 0.0.xx versions, KTCPVS adopts the multiple-thread [[Server Architecture\|server architecture]], because it's easy to implement at early stage.

	== Software ==		== Software ==

@@ Line 30: / Line 30: @@
 See http://www.linuxvirtualserver.org/software/ktcpvs/ktcpvs.html for downloading the KTCPVS software.
-== Examples ==
+== Documentation ==
 * [[Compiling KTCPVS]]
 == Development ==

← Older revision		Revision as of 03:39, 23 February 2007
Line 31:		Line 31:

	== Examples ==		== Examples ==
		+
		+	* [[Compiling KTCPVS]]

	== Development ==		== Development ==

@@ Line 36: / Line 36: @@
 * [[KTCPVS Wish List]]
 [[Category:Load Balancing]]
 [[Category:Terms and Abbreviations]]

← Older revision		Revision as of 06:46, 2 October 2006
Line 25:		Line 25:

	In the KTCPVS, the [[kernel thread]]s are used to parse the content of requests, forward them to backend servers according to scheduling rules, and relay data between client and server. The user-space program tcpvsadm is to administrator KTCPVS, it can write the virtual server rules inside the kernel through setsockopt, and read the KTCPVS rules through getsockopt or /proc file system.		In the KTCPVS, the [[kernel thread]]s are used to parse the content of requests, forward them to backend servers according to scheduling rules, and relay data between client and server. The user-space program tcpvsadm is to administrator KTCPVS, it can write the virtual server rules inside the kernel through setsockopt, and read the KTCPVS rules through getsockopt or /proc file system.
		+
		+	== Software ==
		+
		+	See http://www.linuxvirtualserver.org/software/ktcpvs/ktcpvs.html for downloading the KTCPVS software.

	== Examples ==		== Examples ==

← Older revision		Revision as of 03:57, 27 May 2006
Line 33:		Line 33:

	[[Category:Load Balancing]]		[[Category:Load Balancing]]
		+	[[Category:Terms and Abbreviations]]

@@ Line 1: / Line 1: @@
 == Introduction ==
-KTCPVS stands for Kernel TCP Virtual Server. It implements application-level [[load balancing]] inside the Linux kernel, so called Layer-7 switching. Since the overhead of layer-7 switching in user-space is very high, it is good to implement it inside the kernel in order to avoid the overhead of [[context switching]] and memory copying between user-space and kernel-space. Although the scalability of KTCPVS is lower than that of [[IPVS]] (IP Virtual Server), it is flexible, because the content of request is known before the request is redirected to one server.
+KTCPVS stands for Kernel TCP Virtual Server. It implements application-level [[load balancing]] inside the Linux kernel, so called Layer-7 switching. Since the overhead of layer-7 switching in user-space is very high, it is good to implement it inside the kernel in order to avoid the overhead of [[context switch]]ing and memory copying between user-space and kernel-space. Although the scalability of KTCPVS is lower than that of [[IPVS]] (IP Virtual Server), it is flexible, because the content of request is known before the request is redirected to one server.
 == Architecture ==

@@ Line 24: / Line 24: @@
 [[Image:Ktcpvs impl.jpg|center]]
-In the KTCPVS, the kernel threads are used to parse the content of requests, forward them to backend servers according to scheduling rules, and relay data between client and server. The user-space program tcpvsadm is to administrator KTCPVS, it can write the virtual server rules inside the kernel through setsockopt, and read the KTCPVS rules through getsockopt or /proc file system.
+In the KTCPVS, the [[kernel thread]]s are used to parse the content of requests, forward them to backend servers according to scheduling rules, and relay data between client and server. The user-space program tcpvsadm is to administrator KTCPVS, it can write the virtual server rules inside the kernel through setsockopt, and read the KTCPVS rules through getsockopt or /proc file system.
 == Examples ==

@@ Line 1: / Line 1: @@
 == Introduction ==
-KTCPVS stands for Kernel TCP Virtual Server. It implements application-level load balancing inside the Linux kernel, so called Layer-7 switching. Since the overhead of layer-7 switching in user-space is very high, it is good to implement it inside the kernel in order to avoid the overhead of context switching and memory copying between user-space and kernel-space. Although the scalability of KTCPVS is lower than that of [[IPVS]] (IP Virtual Server), it is flexible, because the content of request is known before the request is redirected to one server.
+KTCPVS stands for Kernel TCP Virtual Server. It implements application-level [[load balancing]] inside the Linux kernel, so called Layer-7 switching. Since the overhead of layer-7 switching in user-space is very high, it is good to implement it inside the kernel in order to avoid the overhead of context switching and memory copying between user-space and kernel-space. Although the scalability of KTCPVS is lower than that of [[IPVS]] (IP Virtual Server), it is flexible, because the content of request is known before the request is redirected to one server.
 == Architecture ==
@@ Line 9: / Line 9: @@
 [[Image:Ktcpvs-architecture.jpg|center]]
-In the system, there are KTCPVS load balancer that can forward requests to different servers according to the content of requests, and backend servers that are running different services. KTCPVS load balancer and backend servers are interconnected through LAN/WAN.
+In the system, there are KTCPVS [[load balancer]] that can forward requests to different servers according to the content of requests, and backend servers that are running different services. KTCPVS [[load balancer]] and backend servers are interconnected through LAN/WAN.
 == Content-based Schedulers ==