CONFIG_IP_VS_LBLCR: locality-based least-connection with replication scheduling

General informations

The Linux kernel configuration item CONFIG_IP_VS_LBLCR has multiple definitions:

locality-based least-connection with replication scheduling found in net/netfilter/ipvs/Kconfig

The configuration item CONFIG_IP_VS_LBLCR:

• prompt: locality-based least-connection with replication scheduling
• type: tristate
• depends on: (none)
• defined in net/netfilter/ipvs/Kconfig
• found in Linux kernels: 2.6.28–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.13
• modules built: ip_vs_lblcr, ip_vs_lblcr

Help text

The locality-based least-connection with replication scheduling algorithm is also for destination IP load balancing. It is usually used in cache cluster. It differs from the LBLC scheduling as follows: the load balancer maintains mappings from a target to a set of server nodes that can serve the target. Requests for a target are assigned to the least-connection node in the target's server set. If all the node in the server set are over loaded, it picks up a least-connection node in the cluster and adds it in the sever set for the target. If the server set has not been modified for the specified time, the most loaded node is removed from the server set, in order to avoid high degree of replication.

If you want to compile it in kernel, say Y. To compile it as a module, choose M here. If unsure, say N.

locality-based least-connection with replication scheduling found in net/ipv4/ipvs/Kconfig

The configuration item CONFIG_IP_VS_LBLCR:

• prompt: locality-based least-connection with replication scheduling
• type: tristate
• depends on: (none)
• defined in net/ipv4/ipvs/Kconfig
• found in Linux kernels: 2.6.0–2.6.27
• modules built: ip_vs_lblcr, ip_vs_lblcr

Help text

The locality-based least-connection with replication scheduling algorithm is also for destination IP load balancing. It is usually used in cache cluster. It differs from the LBLC scheduling as follows: the load balancer maintains mappings from a target to a set of server nodes that can serve the target. Requests for a target are assigned to the least-connection node in the target's server set. If all the node in the server set are over loaded, it picks up a least-connection node in the cluster and adds it in the sever set for the target. If the server set has not been modified for the specified time, the most loaded node is removed from the server set, in order to avoid high degree of replication.

If you want to compile it in kernel, say Y. To compile it as a module, choose M here. If unsure, say N.

Hardware

LKDDb

Raw data from LKDDb:

• lkddb module ip_vs_lblcr CONFIG_IP_VS_LBLCR : net/ipv4/ipvs/Kconfig : "locality-based least-connection with replication scheduling" # in 2.6.0–2.6.27
• lkddb module ip_vs_lblcr CONFIG_IP_VS_LBLCR : net/netfilter/ipvs/Kconfig : "locality-based least-connection with replication scheduling" # in 2.6.28–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.13

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: