Android(安卓)- MPTCP - (./net/ipv4/Kconfig, ./net/mptcp/Kconfig) - android

    注意：不要在 android-x86-6.0-rc1/kernel/ 中执行 make menuconfig
       直接设置 (./net/ipv4/Kconfig, ./net/mptcp/Kconfig) 中的 MPTCP参数
       要使用 Android 本身的编译系统规则。

/opt/android-x86/android-x86-6.0-rc1/kernel.tmp

./net/ipv4/Kconfig

## IP configuration#config IP_MULTICASTbool "IP: multicasting"help  This is code for addressing several networked computers at once,  enlarging your kernel by about 2 KB. You need multicasting if you  intend to participate in the MBONE, a high bandwidth network on top  of the Internet which carries audio and video broadcasts. More  information about the MBONE is on the WWW at  . For most people, it's safe to say N.config IP_ADVANCED_ROUTERbool "IP: advanced router"---help---  If you intend to run your Linux box mostly as a router, i.e. as a  computer that forwards and redistributes network packets, say Y; you  will then be presented with several options that allow more precise  control about the routing process.  The answer to this question won't directly affect the kernel:  answering N will just cause the configurator to skip all the  questions about advanced routing.  Note that your box can only act as a router if you enable IP  forwarding in your kernel; you can do that by saying Y to "/proc  file system support" and "Sysctl support" below and executing the  line  echo "1" > /proc/sys/net/ipv4/ip_forward  at boot time after the /proc file system has been mounted.  If you turn on IP forwarding, you should consider the rp_filter, which  automatically rejects incoming packets if the routing table entry  for their source address doesn't match the network interface they're  arriving on. This has security advantages because it prevents the  so-called IP spoofing, however it can pose problems if you use  asymmetric routing (packets from you to a host take a different path  than packets from that host to you) or if you operate a non-routing  host which has several IP addresses on different interfaces. To turn  rp_filter on use:  echo 1 > /proc/sys/net/ipv4/conf//rp_filter   or  echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter  Note that some distributions enable it in startup scripts.  For details about rp_filter strict and loose mode read  .  If unsure, say N here.config IP_FIB_TRIE_STATSbool "FIB TRIE statistics"depends on IP_ADVANCED_ROUTER---help---  Keep track of statistics on structure of FIB TRIE table.  Useful for testing and measuring TRIE performance.config IP_MULTIPLE_TABLESbool "IP: policy routing"depends on IP_ADVANCED_ROUTERselect FIB_RULES---help---  Normally, a router decides what to do with a received packet based  solely on the packet's final destination address. If you say Y here,  the Linux router will also be able to take the packet's source  address into account. Furthermore, the TOS (Type-Of-Service) field  of the packet can be used for routing decisions as well.  If you are interested in this, please see the preliminary  documentation at   and .  You will need supporting software from  .  If unsure, say N.config IP_ROUTE_MULTIPATHbool "IP: equal cost multipath"depends on IP_ADVANCED_ROUTERhelp  Normally, the routing tables specify a single action to be taken in  a deterministic manner for a given packet. If you say Y here  however, it becomes possible to attach several actions to a packet  pattern, in effect specifying several alternative paths to travel  for those packets. The router considers all these paths to be of  equal "cost" and chooses one of them in a non-deterministic fashion  if a matching packet arrives.config IP_ROUTE_VERBOSEbool "IP: verbose route monitoring"depends on IP_ADVANCED_ROUTERhelp  If you say Y here, which is recommended, then the kernel will print  verbose messages regarding the routing, for example warnings about  received packets which look strange and could be evidence of an  attack or a misconfigured system somewhere. The information is  handled by the klogd daemon which is responsible for kernel messages  ("man klogd").config IP_ROUTE_CLASSIDboolconfig IP_PNPbool "IP: kernel level autoconfiguration"help  This enables automatic configuration of IP addresses of devices and  of the routing table during kernel boot, based on either information  supplied on the kernel command line or by BOOTP or RARP protocols.  You need to say Y only for diskless machines requiring network  access to boot (in which case you want to say Y to "Root file system  on NFS" as well), because all other machines configure the network  in their startup scripts.config IP_PNP_DHCPbool "IP: DHCP support"depends on IP_PNP---help---  If you want your Linux box to mount its whole root file system (the  one containing the directory /) from some other computer over the  net via NFS and you want the IP address of your computer to be  discovered automatically at boot time using the DHCP protocol (a  special protocol designed for doing this job), say Y here. In case  the boot ROM of your network card was designed for booting Linux and  does DHCP itself, providing all necessary information on the kernel  command line, you can say N here.  If unsure, say Y. Note that if you want to use DHCP, a DHCP server  must be operating on your network.  Read   for details.config IP_PNP_BOOTPbool "IP: BOOTP support"depends on IP_PNP---help---  If you want your Linux box to mount its whole root file system (the  one containing the directory /) from some other computer over the  net via NFS and you want the IP address of your computer to be  discovered automatically at boot time using the BOOTP protocol (a  special protocol designed for doing this job), say Y here. In case  the boot ROM of your network card was designed for booting Linux and  does BOOTP itself, providing all necessary information on the kernel  command line, you can say N here. If unsure, say Y. Note that if you  want to use BOOTP, a BOOTP server must be operating on your network.  Read  for details.config IP_PNP_RARPbool "IP: RARP support"depends on IP_PNPhelp  If you want your Linux box to mount its whole root file system (the  one containing the directory /) from some other computer over the  net via NFS and you want the IP address of your computer to be  discovered automatically at boot time using the RARP protocol (an  older protocol which is being obsoleted by BOOTP and DHCP), say Y  here. Note that if you want to use RARP, a RARP server must be  operating on your network. Read   for details.config NET_IPIPtristate "IP: tunneling"select INET_TUNNELselect NET_IP_TUNNEL---help---  Tunneling means encapsulating data of one protocol type within  another protocol and sending it over a channel that understands the  encapsulating protocol. This particular tunneling driver implements  encapsulation of IP within IP, which sounds kind of pointless, but  can be useful if you want to make your (or some other) machine  appear on a different network than it physically is, or to use  mobile-IP facilities (allowing laptops to seamlessly move between  networks without changing their IP addresses).  Saying Y to this option will produce two modules ( = code which can  be inserted in and removed from the running kernel whenever you  want). Most people won't need this and can say N.config NET_IPGRE_DEMUXtristate "IP: GRE demultiplexer"help This is helper module to demultiplex GRE packets on GRE version field criteria. Required by ip_gre and pptp modules.config NET_IP_TUNNELtristatedefault nconfig NET_IPGREtristate "IP: GRE tunnels over IP"depends on (IPV6 || IPV6=n) && NET_IPGRE_DEMUXselect NET_IP_TUNNELhelp  Tunneling means encapsulating data of one protocol type within  another protocol and sending it over a channel that understands the  encapsulating protocol. This particular tunneling driver implements  GRE (Generic Routing Encapsulation) and at this time allows  encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.  This driver is useful if the other endpoint is a Cisco router: Cisco  likes GRE much better than the other Linux tunneling driver ("IP  tunneling" above). In addition, GRE allows multicast redistribution  through the tunnel.config NET_IPGRE_BROADCASTbool "IP: broadcast GRE over IP"depends on IP_MULTICAST && NET_IPGREhelp  One application of GRE/IP is to construct a broadcast WAN (Wide Area  Network), which looks like a normal Ethernet LAN (Local Area  Network), but can be distributed all over the Internet. If you want  to do that, say Y here and to "IP multicast routing" below.config IP_MROUTEbool "IP: multicast routing"depends on IP_MULTICASThelp  This is used if you want your machine to act as a router for IP  packets that have several destination addresses. It is needed on the  MBONE, a high bandwidth network on top of the Internet which carries  audio and video broadcasts. In order to do that, you would most  likely run the program mrouted. If you haven't heard about it, you  don't need it.config IP_MROUTE_MULTIPLE_TABLESbool "IP: multicast policy routing"depends on IP_MROUTE && IP_ADVANCED_ROUTERselect FIB_RULEShelp  Normally, a multicast router runs a userspace daemon and decides  what to do with a multicast packet based on the source and  destination addresses. If you say Y here, the multicast router  will also be able to take interfaces and packet marks into  account and run multiple instances of userspace daemons  simultaneously, each one handling a single table.  If unsure, say N.config IP_PIMSM_V1bool "IP: PIM-SM version 1 support"depends on IP_MROUTEhelp  Kernel side support for Sparse Mode PIM (Protocol Independent  Multicast) version 1. This multicast routing protocol is used widely  because Cisco supports it. You need special software to use it  (pimd-v1). Please see  for more  information about PIM.  Say Y if you want to use PIM-SM v1. Note that you can say N here if  you just want to use Dense Mode PIM.config IP_PIMSM_V2bool "IP: PIM-SM version 2 support"depends on IP_MROUTEhelp  Kernel side support for Sparse Mode PIM version 2. In order to use  this, you need an experimental routing daemon supporting it (pimd or  gated-5). This routing protocol is not used widely, so say N unless  you want to play with it.config SYN_COOKIESbool "IP: TCP syncookie support"---help---  Normal TCP/IP networking is open to an attack known as "SYN  flooding". This denial-of-service attack prevents legitimate remote  users from being able to connect to your computer during an ongoing  attack and requires very little work from the attacker, who can  operate from anywhere on the Internet.  SYN cookies provide protection against this type of attack. If you  say Y here, the TCP/IP stack will use a cryptographic challenge  protocol known as "SYN cookies" to enable legitimate users to  continue to connect, even when your machine is under attack. There  is no need for the legitimate users to change their TCP/IP software;  SYN cookies work transparently to them. For technical information  about SYN cookies, check out .  If you are SYN flooded, the source address reported by the kernel is  likely to have been forged by the attacker; it is only reported as  an aid in tracing the packets to their actual source and should not  be taken as absolute truth.  SYN cookies may prevent correct error reporting on clients when the  server is really overloaded. If this happens frequently better turn  them off.  If you say Y here, you can disable SYN cookies at run time by  saying Y to "/proc file system support" and  "Sysctl support" below and executing the command  echo 0 > /proc/sys/net/ipv4/tcp_syncookies  after the /proc file system has been mounted.  If unsure, say N.config NET_IPVTItristate "Virtual (secure) IP: tunneling"select INET_TUNNELselect NET_IP_TUNNELdepends on INET_XFRM_MODE_TUNNEL---help---  Tunneling means encapsulating data of one protocol type within  another protocol and sending it over a channel that understands the  encapsulating protocol. This can be used with xfrm mode tunnel to give  the notion of a secure tunnel for IPSEC and then use routing protocol  on top.config NET_UDP_TUNNELtristateselect NET_IP_TUNNELdefault nconfig NET_FOUtristate "IP: Foo (IP protocols) over UDP"select XFRMselect NET_UDP_TUNNEL---help---  Foo over UDP allows any IP protocol to be directly encapsulated  over UDP include tunnels (IPIP, GRE, SIT). By encapsulating in UDP  network mechanisms and optimizations for UDP (such as ECMP  and RSS) can be leveraged to provide better service.config NET_FOU_IP_TUNNELSbool "IP: FOU encapsulation of IP tunnels"depends on NET_IPIP || NET_IPGRE || IPV6_SITselect NET_FOU---help---  Allow configuration of FOU or GUE encapsulation for IP tunnels.  When this option is enabled IP tunnels can be configured to use  FOU or GUE encapsulation.config INET_AHtristate "IP: AH transformation"select XFRM_ALGOselect CRYPTOselect CRYPTO_HMACselect CRYPTO_MD5select CRYPTO_SHA1---help---  Support for IPsec AH.  If unsure, say Y.config INET_ESPtristate "IP: ESP transformation"select XFRM_ALGOselect CRYPTOselect CRYPTO_AUTHENCselect CRYPTO_HMACselect CRYPTO_MD5select CRYPTO_CBCselect CRYPTO_SHA1select CRYPTO_DES---help---  Support for IPsec ESP.  If unsure, say Y.config INET_IPCOMPtristate "IP: IPComp transformation"select INET_XFRM_TUNNELselect XFRM_IPCOMP---help---  Support for IP Payload Compression Protocol (IPComp) (RFC3173),  typically needed for IPsec.  If unsure, say Y.config INET_XFRM_TUNNELtristateselect INET_TUNNELdefault nconfig INET_TUNNELtristatedefault nconfig INET_XFRM_MODE_TRANSPORTtristate "IP: IPsec transport mode"default yselect XFRM---help---  Support for IPsec transport mode.  If unsure, say Y.config INET_XFRM_MODE_TUNNELtristate "IP: IPsec tunnel mode"default yselect XFRM---help---  Support for IPsec tunnel mode.  If unsure, say Y.config INET_XFRM_MODE_BEETtristate "IP: IPsec BEET mode"default yselect XFRM---help---  Support for IPsec BEET mode.  If unsure, say Y.config INET_LROtristate "Large Receive Offload (ipv4/tcp)"default y---help---  Support for Large Receive Offload (ipv4/tcp).  If unsure, say Y.config INET_DIAGtristate "INET: socket monitoring interface"default y---help---  Support for INET (TCP, DCCP, etc) socket monitoring interface used by  native Linux tools such as ss. ss is included in iproute2, currently  downloadable at:      http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2  If unsure, say Y.config INET_TCP_DIAGdepends on INET_DIAGdef_tristate INET_DIAGconfig INET_UDP_DIAGtristate "UDP: socket monitoring interface"depends on INET_DIAG && (IPV6 || IPV6=n)default n---help---  Support for UDP socket monitoring interface used by the ss tool.  If unsure, say Y.config INET_DIAG_DESTROYbool "INET: allow privileged process to administratively close sockets"depends on INET_DIAGdefault n---help---  Provides a SOCK_DESTROY operation that allows privileged processes  (e.g., a connection manager or a network administration tool such as  ss) to close sockets opened by other processes. Closing a socket in  this way interrupts any blocking read/write/connect operations on  the socket and causes future socket calls to behave as if the socket  had been disconnected.  If unsure, say N.menuconfig TCP_CONG_ADVANCEDbool "TCP: advanced congestion control"---help---  Support for selection of various TCP congestion control  modules.  Nearly all users can safely say no here, and a safe default  selection will be made (CUBIC with new Reno as a fallback).  If unsure, say N.if TCP_CONG_ADVANCEDconfig TCP_CONG_BICtristate "Binary Increase Congestion (BIC) control"default m---help---BIC-TCP is a sender-side only change that ensures a linear RTTfairness under large windows while offering both scalability andbounded TCP-friendliness. The protocol combines two schemescalled additive increase and binary search increase. When thecongestion window is large, additive increase with a largeincrement ensures linear RTT fairness as well as goodscalability. Under small congestion windows, binary searchincrease provides TCP friendliness.See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/config TCP_CONG_CUBICtristate "CUBIC TCP"default y---help---This is version 2.0 of BIC-TCP which uses a cubic growth functionamong other techniques.config TCP_CONG_WESTWOODtristate "TCP Westwood+"default m---help---TCP Westwood+ is a sender-side only modification of the TCP Renoprotocol stack that optimizes the performance of TCP congestioncontrol. It is based on end-to-end bandwidth estimation to setcongestion window and slow start threshold after a congestionepisode. Using this estimation, TCP Westwood+ adaptively sets aslow start threshold and a congestion window which takes intoaccount the bandwidth used  at the time congestion is experienced.TCP Westwood+ significantly increases fairness wrt TCP Reno inwired networks and throughput over wireless links.config TCP_CONG_HTCP        tristate "H-TCP"        default m---help---H-TCP is a send-side only modifications of the TCP Renoprotocol stack that optimizes the performance of TCPcongestion control for high speed network links. It uses amodeswitch to change the alpha and beta parameters of TCP Renobased on network conditions and in a way so as to be fair withother Reno and H-TCP flows.config TCP_CONG_HSTCPtristate "High Speed TCP"default n---help---Sally Floyd's High Speed TCP (RFC 3649) congestion control.A modification to TCP's congestion control mechanism for usewith large congestion windows. A table indicates how much toincrease the congestion window by when an ACK is received.For more detailsee http://www.icir.org/floyd/hstcp.htmlconfig TCP_CONG_HYBLAtristate "TCP-Hybla congestion control algorithm"default n---help---TCP-Hybla is a sender-side only change that eliminates penalization oflong-RTT, large-bandwidth connections, like when satellite legs areinvolved, especially when sharing a common bottleneck with normalterrestrial connections.config TCP_CONG_VEGAStristate "TCP Vegas"default n---help---TCP Vegas is a sender-side only change to TCP that anticipatesthe onset of congestion by estimating the bandwidth. TCP Vegasadjusts the sending rate by modifying the congestionwindow. TCP Vegas should provide less packet loss, but it isnot as aggressive as TCP Reno.config TCP_CONG_SCALABLEtristate "Scalable TCP"default n---help---Scalable TCP is a sender-side only change to TCP which uses aMIMD congestion control algorithm which has some nice scalingproperties, though is known to have fairness issues.See http://www.deneholme.net/tom/scalable/config TCP_CONG_LPtristate "TCP Low Priority"default n---help---TCP Low Priority (TCP-LP), a distributed algorithm whose goal isto utilize only the excess network bandwidth as compared to the``fair share`` of bandwidth as targeted by TCP.See http://www-ece.rice.edu/networks/TCP-LP/config TCP_CONG_VENOtristate "TCP Veno"default n---help---TCP Veno is a sender-side only enhancement of TCP to obtain betterthroughput over wireless networks. TCP Veno makes use of statedistinguishing to circumvent the difficult judgment of the packet losstype. TCP Veno cuts down less congestion window in response to randomloss packets.See  config TCP_CONG_YEAHtristate "YeAH TCP"select TCP_CONG_VEGASdefault n---help---YeAH-TCP is a sender-side high-speed enabled TCP congestion controlalgorithm, which uses a mixed loss/delay approach to compute thecongestion window. It's design goals target high efficiency,internal, RTT and Reno fairness, resilience to link loss whilekeeping network elements load as low as possible.For further details look here:  http://wil.cs.caltech.edu/pfldnet2007/paper/YeAH_TCP.pdfconfig TCP_CONG_ILLINOIStristate "TCP Illinois"default n---help---TCP-Illinois is a sender-side modification of TCP Reno forhigh speed long delay links. It uses round-trip-time toadjust the alpha and beta parameters to achieve a higher averagethroughput and maintain fairness.For further details see:  http://www.ews.uiuc.edu/~shaoliu/tcpillinois/index.htmlconfig TCP_CONG_DCTCPtristate "DataCenter TCP (DCTCP)"default n---help---DCTCP leverages Explicit Congestion Notification (ECN) in the network toprovide multi-bit feedback to the end hosts. It is designed to provide:- High burst tolerance (incast due to partition/aggregate),- Low latency (short flows, queries),- High throughput (continuous data updates, large file transfers) with  commodity, shallow-buffered switches.All switches in the data center network running DCTCP must supportECN marking and be configured for marking when reaching defined switchbuffer thresholds. The default ECN marking threshold heuristic forDCTCP on switches is 20 packets (30KB) at 1Gbps, and 65 packets(~100KB) at 10Gbps, but might need further careful tweaking.For further details see:  http://simula.stanford.edu/~alizade/Site/DCTCP_files/dctcp-final.pdfconfig TCP_CONG_LIAtristate "MPTCP Linked Increase"depends on MPTCPdefault y---help---MultiPath TCP Linked Increase Congestion ControlTo enable it, just put 'lia' in tcp_congestion_controlconfig TCP_CONG_OLIAtristate "MPTCP Opportunistic Linked Increase"depends on MPTCPdefault y---help---MultiPath TCP Opportunistic Linked Increase Congestion ControlTo enable it, just put 'olia' in tcp_congestion_controlconfig TCP_CONG_WVEGAStristate "MPTCP WVEGAS CONGESTION CONTROL"depends on MPTCPdefault y---help---wVegas congestion control for MPTCPTo enable it, just put 'wvegas' in tcp_congestion_controlconfig TCP_CONG_BALIAtristate "MPTCP BALIA CONGESTION CONTROL"depends on MPTCPdefault y---help---Multipath TCP Balanced Linked Adaptation Congestion ControlTo enable it, just put 'balia' in tcp_congestion_controlconfig TCP_CONG_CDGtristate "CAIA Delay-Gradient (CDG)"default n---help---CAIA Delay-Gradient (CDG) is a TCP congestion control that modifiesthe TCP sender in order to:  o Use the delay gradient as a congestion signal.  o Back off with an average probability that is independent of the RTT.  o Coexist with flows that use loss-based congestion control.  o Tolerate packet loss unrelated to congestion.For further details see:  D.A. Hayes and G. Armitage. "Revisiting TCP congestion control using  delay gradients." In Networking 2011. Preprint: http://goo.gl/No3vdgchoiceprompt "Default TCP congestion control"default DEFAULT_LIAhelp  Select the TCP congestion control that will be used by default  for all connections.config DEFAULT_BICbool "Bic" if TCP_CONG_BIC=y#config DEFAULT_CUBIC#bool "Cubic" if TCP_CONG_CUBIC=yconfig DEFAULT_HTCPbool "Htcp" if TCP_CONG_HTCP=yconfig DEFAULT_HYBLAbool "Hybla" if TCP_CONG_HYBLA=yconfig DEFAULT_VEGASbool "Vegas" if TCP_CONG_VEGAS=yconfig DEFAULT_VENObool "Veno" if TCP_CONG_VENO=yconfig DEFAULT_WESTWOODbool "Westwood" if TCP_CONG_WESTWOOD=yconfig DEFAULT_DCTCPbool "DCTCP" if TCP_CONG_DCTCP=yconfig DEFAULT_LIAbool "Lia" if TCP_CONG_LIA=yconfig DEFAULT_OLIAbool "Olia" if TCP_CONG_OLIA=yconfig DEFAULT_WVEGASbool "Wvegas" if TCP_CONG_WVEGAS=yconfig DEFAULT_BALIAbool "Balia" if TCP_CONG_BALIA=yconfig DEFAULT_CDGbool "CDG" if TCP_CONG_CDG=yconfig DEFAULT_RENObool "Reno"endchoiceendifconfig TCP_CONG_CUBICtristatedepends on !TCP_CONG_ADVANCEDdefault yconfig DEFAULT_TCP_CONGstringdefault "bic" if DEFAULT_BICdefault "cubic" if DEFAULT_CUBICdefault "htcp" if DEFAULT_HTCPdefault "hybla" if DEFAULT_HYBLAdefault "vegas" if DEFAULT_VEGASdefault "westwood" if DEFAULT_WESTWOODdefault "veno" if DEFAULT_VENOdefault "lia" if DEFAULT_LIAdefault "olia" if DEFAULT_OLIAdefault "wvegas" if DEFAULT_WVEGASdefault "balia" if DEFAULT_BALIAdefault "reno" if DEFAULT_RENOdefault "dctcp" if DEFAULT_DCTCPdefault "cdg" if DEFAULT_CDGdefault "cubic"config TCP_MD5SIGbool "TCP: MD5 Signature Option support (RFC2385)"select CRYPTOselect CRYPTO_MD5---help---  RFC2385 specifies a method of giving MD5 protection to TCP sessions.  Its main (only?) use is to protect BGP sessions between core routers  on the Internet.  If unsure, say N.

./net/mptcp/Kconfig

## MPTCP configuration#config MPTCPbool "MPTCP protocol"depends on IPV6 || IPV6=ndefault y---help---  This replaces the normal TCP stack with a Multipath TCP stack,  able to use several paths at once.menuconfig MPTCP_PM_ADVANCEDbool "MPTCP: advanced path-manager control"depends on MPTCPdefault y---help---  Support for selection of different path-managers. You should choose 'Y' here,  because otherwise you will not actively create new MPTCP-subflows.if MPTCP_PM_ADVANCEDconfig MPTCP_FULLMESHtristate "MPTCP Full-Mesh Path-Manager"depends on MPTCPdefault y---help---  This path-management module will create a full-mesh among all IP-addresses.config MPTCP_NDIFFPORTStristate "MPTCP ndiff-ports"depends on MPTCPdefault y---help---  This path-management module will create multiple subflows between the same  pair of IP-addresses, modifying the source-port. You can set the number  of subflows via the mptcp_ndiffports-sysctl.config MPTCP_BINDERtristate "MPTCP Binder"depends on MPTCP---help---  This path-management module works like ndiffports, and adds the sysctl  option to set the gateway (and/or path to) per each additional subflow  via Loose Source Routing (IPv4 only).choiceprompt "Default MPTCP Path-Manager"default DEFAULT_FULLMESHhelp  Select the Path-Manager of your choiceconfig DEFAULT_FULLMESHbool "Full mesh" if MPTCP_FULLMESH=yconfig DEFAULT_NDIFFPORTSbool "ndiff-ports" if MPTCP_NDIFFPORTS=yconfig DEFAULT_BINDERbool "binder" if MPTCP_BINDER=yconfig DEFAULT_DUMMYbool "Default"endchoiceendifconfig DEFAULT_MPTCP_PMstringdefault "default" if DEFAULT_DUMMYdefault "fullmesh" if DEFAULT_FULLMESH default "ndiffports" if DEFAULT_NDIFFPORTSdefault "binder" if DEFAULT_BINDERdefault "default"menuconfig MPTCP_SCHED_ADVANCEDbool "MPTCP: advanced scheduler control"depends on MPTCP---help---  Support for selection of different schedulers. You should choose 'Y' here,  if you want to choose a different scheduler than the default one.if MPTCP_SCHED_ADVANCEDconfig MPTCP_ROUNDROBINtristate "MPTCP Round-Robin"depends on MPTCP---help---  This is a very simple round-robin scheduler. Probably has bad performance  but might be interesting for researchers.config MPTCP_REDUNDANTtristate "MPTCP Redundant"depends on MPTCP---help---  This scheduler sends all packets redundantly over all subflows to decreases  latency and jitter on the cost of lower throughput.choiceprompt "Default MPTCP Scheduler"default DEFAULThelp  Select the Scheduler of your choiceconfig DEFAULT_SCHEDULERbool "Default"---help---  This is the default scheduler, sending first on the subflow  with the lowest RTT.config DEFAULT_ROUNDROBINbool "Round-Robin" if MPTCP_ROUNDROBIN=y---help---  This is the round-rob scheduler, sending in a round-robin  fashion..config DEFAULT_REDUNDANTbool "Redundant" if MPTCP_REDUNDANT=y---help---  This is the redundant scheduler, sending packets redundantly over  all the subflows.endchoiceendifconfig DEFAULT_MPTCP_SCHEDstringdepends on MPTCPdefault "default" if DEFAULT_SCHEDULERdefault "roundrobin" if DEFAULT_ROUNDROBINdefault "redundant" if DEFAULT_REDUNDANTdefault "default"

Android(安卓)- MPTCP - (./net/ipv4/Kconfig, ./net/mptcp/Kconfig)

更多相关文章

随机推荐