1 # SPDX-License-Identifier: GPL-2.0-only <<
2 # 1 #
3 # Traffic control configuration. 2 # Traffic control configuration.
4 # !! 3 #
5 4
6 menuconfig NET_SCHED 5 menuconfig NET_SCHED
7 bool "QoS and/or fair queueing" 6 bool "QoS and/or fair queueing"
8 select NET_SCH_FIFO 7 select NET_SCH_FIFO
9 help !! 8 ---help---
10 When the kernel has several packets 9 When the kernel has several packets to send out over a network
11 device, it has to decide which ones 10 device, it has to decide which ones to send first, which ones to
12 delay, and which ones to drop. This 11 delay, and which ones to drop. This is the job of the queueing
13 disciplines, several different algor 12 disciplines, several different algorithms for how to do this
14 "fairly" have been proposed. 13 "fairly" have been proposed.
15 14
16 If you say N here, you will get the 15 If you say N here, you will get the standard packet scheduler, which
17 is a FIFO (first come, first served) 16 is a FIFO (first come, first served). If you say Y here, you will be
18 able to choose from among several al 17 able to choose from among several alternative algorithms which can
19 then be attached to different networ 18 then be attached to different network devices. This is useful for
20 example if some of your network devi 19 example if some of your network devices are real time devices that
21 need a certain minimum data flow rat 20 need a certain minimum data flow rate, or if you need to limit the
22 maximum data flow rate for traffic w 21 maximum data flow rate for traffic which matches specified criteria.
23 This code is considered to be experi 22 This code is considered to be experimental.
24 23
25 To administer these schedulers, you' 24 To administer these schedulers, you'll need the user-level utilities
26 from the package iproute2+tc at 25 from the package iproute2+tc at
27 <https://www.kernel.org/pub/linux/ut 26 <https://www.kernel.org/pub/linux/utils/net/iproute2/>. That package
28 also contains some documentation; fo 27 also contains some documentation; for more, check out
29 <http://www.linuxfoundation.org/coll 28 <http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2>.
30 29
31 This Quality of Service (QoS) suppor 30 This Quality of Service (QoS) support will enable you to use
32 Differentiated Services (diffserv) a 31 Differentiated Services (diffserv) and Resource Reservation Protocol
33 (RSVP) on your Linux router if you a 32 (RSVP) on your Linux router if you also say Y to the corresponding
34 classifiers below. Documentation an 33 classifiers below. Documentation and software is at
35 <http://diffserv.sourceforge.net/>. 34 <http://diffserv.sourceforge.net/>.
36 35
37 If you say Y here and to "/proc file 36 If you say Y here and to "/proc file system" below, you will be able
38 to read status information about pac 37 to read status information about packet schedulers from the file
39 /proc/net/psched. 38 /proc/net/psched.
40 39
41 The available schedulers are listed 40 The available schedulers are listed in the following questions; you
42 can say Y to as many as you like. If 41 can say Y to as many as you like. If unsure, say N now.
43 42
44 if NET_SCHED 43 if NET_SCHED
45 44
46 comment "Queueing/Scheduling" 45 comment "Queueing/Scheduling"
47 46
>> 47 config NET_SCH_CBQ
>> 48 tristate "Class Based Queueing (CBQ)"
>> 49 ---help---
>> 50 Say Y here if you want to use the Class-Based Queueing (CBQ) packet
>> 51 scheduling algorithm. This algorithm classifies the waiting packets
>> 52 into a tree-like hierarchy of classes; the leaves of this tree are
>> 53 in turn scheduled by separate algorithms.
>> 54
>> 55 See the top of <file:net/sched/sch_cbq.c> for more details.
>> 56
>> 57 CBQ is a commonly used scheduler, so if you're unsure, you should
>> 58 say Y here. Then say Y to all the queueing algorithms below that you
>> 59 want to use as leaf disciplines.
>> 60
>> 61 To compile this code as a module, choose M here: the
>> 62 module will be called sch_cbq.
>> 63
48 config NET_SCH_HTB 64 config NET_SCH_HTB
49 tristate "Hierarchical Token Bucket (H 65 tristate "Hierarchical Token Bucket (HTB)"
50 help !! 66 ---help---
51 Say Y here if you want to use the Hi 67 Say Y here if you want to use the Hierarchical Token Buckets (HTB)
52 packet scheduling algorithm. See 68 packet scheduling algorithm. See
53 <http://luxik.cdi.cz/~devik/qos/htb/ 69 <http://luxik.cdi.cz/~devik/qos/htb/> for complete manual and
54 in-depth articles. 70 in-depth articles.
55 71
56 HTB is very similar to CBQ regarding 72 HTB is very similar to CBQ regarding its goals however is has
57 different properties and different a 73 different properties and different algorithm.
58 74
59 To compile this code as a module, ch 75 To compile this code as a module, choose M here: the
60 module will be called sch_htb. 76 module will be called sch_htb.
61 77
62 config NET_SCH_HFSC 78 config NET_SCH_HFSC
63 tristate "Hierarchical Fair Service Cu 79 tristate "Hierarchical Fair Service Curve (HFSC)"
64 help !! 80 ---help---
65 Say Y here if you want to use the Hi 81 Say Y here if you want to use the Hierarchical Fair Service Curve
66 (HFSC) packet scheduling algorithm. 82 (HFSC) packet scheduling algorithm.
67 83
68 To compile this code as a module, ch 84 To compile this code as a module, choose M here: the
69 module will be called sch_hfsc. 85 module will be called sch_hfsc.
70 86
>> 87 config NET_SCH_ATM
>> 88 tristate "ATM Virtual Circuits (ATM)"
>> 89 depends on ATM
>> 90 ---help---
>> 91 Say Y here if you want to use the ATM pseudo-scheduler. This
>> 92 provides a framework for invoking classifiers, which in turn
>> 93 select classes of this queuing discipline. Each class maps
>> 94 the flow(s) it is handling to a given virtual circuit.
>> 95
>> 96 See the top of <file:net/sched/sch_atm.c> for more details.
>> 97
>> 98 To compile this code as a module, choose M here: the
>> 99 module will be called sch_atm.
>> 100
71 config NET_SCH_PRIO 101 config NET_SCH_PRIO
72 tristate "Multi Band Priority Queueing 102 tristate "Multi Band Priority Queueing (PRIO)"
73 help !! 103 ---help---
74 Say Y here if you want to use an n-b 104 Say Y here if you want to use an n-band priority queue packet
75 scheduler. 105 scheduler.
76 106
77 To compile this code as a module, ch 107 To compile this code as a module, choose M here: the
78 module will be called sch_prio. 108 module will be called sch_prio.
79 109
80 config NET_SCH_MULTIQ 110 config NET_SCH_MULTIQ
81 tristate "Hardware Multiqueue-aware Mu 111 tristate "Hardware Multiqueue-aware Multi Band Queuing (MULTIQ)"
82 help !! 112 ---help---
83 Say Y here if you want to use an n-b 113 Say Y here if you want to use an n-band queue packet scheduler
84 to support devices that have multipl 114 to support devices that have multiple hardware transmit queues.
85 115
86 To compile this code as a module, ch 116 To compile this code as a module, choose M here: the
87 module will be called sch_multiq. 117 module will be called sch_multiq.
88 118
89 config NET_SCH_RED 119 config NET_SCH_RED
90 tristate "Random Early Detection (RED) 120 tristate "Random Early Detection (RED)"
91 help !! 121 ---help---
92 Say Y here if you want to use the Ra 122 Say Y here if you want to use the Random Early Detection (RED)
93 packet scheduling algorithm. 123 packet scheduling algorithm.
94 124
95 See the top of <file:net/sched/sch_r 125 See the top of <file:net/sched/sch_red.c> for more details.
96 126
97 To compile this code as a module, ch 127 To compile this code as a module, choose M here: the
98 module will be called sch_red. 128 module will be called sch_red.
99 129
100 config NET_SCH_SFB 130 config NET_SCH_SFB
101 tristate "Stochastic Fair Blue (SFB)" 131 tristate "Stochastic Fair Blue (SFB)"
102 help !! 132 ---help---
103 Say Y here if you want to use the St 133 Say Y here if you want to use the Stochastic Fair Blue (SFB)
104 packet scheduling algorithm. 134 packet scheduling algorithm.
105 135
106 See the top of <file:net/sched/sch_s 136 See the top of <file:net/sched/sch_sfb.c> for more details.
107 137
108 To compile this code as a module, ch 138 To compile this code as a module, choose M here: the
109 module will be called sch_sfb. 139 module will be called sch_sfb.
110 140
111 config NET_SCH_SFQ 141 config NET_SCH_SFQ
112 tristate "Stochastic Fairness Queueing 142 tristate "Stochastic Fairness Queueing (SFQ)"
113 help !! 143 ---help---
114 Say Y here if you want to use the St 144 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
115 packet scheduling algorithm. 145 packet scheduling algorithm.
116 146
117 See the top of <file:net/sched/sch_s 147 See the top of <file:net/sched/sch_sfq.c> for more details.
118 148
119 To compile this code as a module, ch 149 To compile this code as a module, choose M here: the
120 module will be called sch_sfq. 150 module will be called sch_sfq.
121 151
122 config NET_SCH_TEQL 152 config NET_SCH_TEQL
123 tristate "True Link Equalizer (TEQL)" 153 tristate "True Link Equalizer (TEQL)"
124 help !! 154 ---help---
125 Say Y here if you want to use the Tr 155 Say Y here if you want to use the True Link Equalizer (TLE) packet
126 scheduling algorithm. This queueing 156 scheduling algorithm. This queueing discipline allows the combination
127 of several physical devices into one 157 of several physical devices into one virtual device.
128 158
129 See the top of <file:net/sched/sch_t 159 See the top of <file:net/sched/sch_teql.c> for more details.
130 160
131 To compile this code as a module, ch 161 To compile this code as a module, choose M here: the
132 module will be called sch_teql. 162 module will be called sch_teql.
133 163
134 config NET_SCH_TBF 164 config NET_SCH_TBF
135 tristate "Token Bucket Filter (TBF)" 165 tristate "Token Bucket Filter (TBF)"
136 help !! 166 ---help---
137 Say Y here if you want to use the To 167 Say Y here if you want to use the Token Bucket Filter (TBF) packet
138 scheduling algorithm. 168 scheduling algorithm.
139 169
140 See the top of <file:net/sched/sch_t 170 See the top of <file:net/sched/sch_tbf.c> for more details.
141 171
142 To compile this code as a module, ch 172 To compile this code as a module, choose M here: the
143 module will be called sch_tbf. 173 module will be called sch_tbf.
144 174
145 config NET_SCH_CBS <<
146 tristate "Credit Based Shaper (CBS)" <<
147 help <<
148 Say Y here if you want to use the Cr <<
149 scheduling algorithm. <<
150 <<
151 See the top of <file:net/sched/sch_c <<
152 <<
153 To compile this code as a module, ch <<
154 module will be called sch_cbs. <<
155 <<
156 config NET_SCH_ETF <<
157 tristate "Earliest TxTime First (ETF)" <<
158 help <<
159 Say Y here if you want to use the Ea <<
160 scheduling algorithm. <<
161 <<
162 See the top of <file:net/sched/sch_e <<
163 <<
164 To compile this code as a module, ch <<
165 module will be called sch_etf. <<
166 <<
167 config NET_SCH_MQPRIO_LIB <<
168 tristate <<
169 help <<
170 Common library for manipulating mqpr <<
171 <<
172 config NET_SCH_TAPRIO <<
173 tristate "Time Aware Priority (taprio) <<
174 select NET_SCH_MQPRIO_LIB <<
175 help <<
176 Say Y here if you want to use the Ti <<
177 scheduling algorithm. <<
178 <<
179 See the top of <file:net/sched/sch_t <<
180 <<
181 To compile this code as a module, ch <<
182 module will be called sch_taprio. <<
183 <<
184 config NET_SCH_GRED 175 config NET_SCH_GRED
185 tristate "Generic Random Early Detecti 176 tristate "Generic Random Early Detection (GRED)"
186 help !! 177 ---help---
187 Say Y here if you want to use the Ge 178 Say Y here if you want to use the Generic Random Early Detection
188 (GRED) packet scheduling algorithm f 179 (GRED) packet scheduling algorithm for some of your network devices
189 (see the top of <file:net/sched/sch_ 180 (see the top of <file:net/sched/sch_red.c> for details and
190 references about the algorithm). 181 references about the algorithm).
191 182
192 To compile this code as a module, ch 183 To compile this code as a module, choose M here: the
193 module will be called sch_gred. 184 module will be called sch_gred.
194 185
>> 186 config NET_SCH_DSMARK
>> 187 tristate "Differentiated Services marker (DSMARK)"
>> 188 ---help---
>> 189 Say Y if you want to schedule packets according to the
>> 190 Differentiated Services architecture proposed in RFC 2475.
>> 191 Technical information on this method, with pointers to associated
>> 192 RFCs, is available at <http://www.gta.ufrj.br/diffserv/>.
>> 193
>> 194 To compile this code as a module, choose M here: the
>> 195 module will be called sch_dsmark.
>> 196
195 config NET_SCH_NETEM 197 config NET_SCH_NETEM
196 tristate "Network emulator (NETEM)" 198 tristate "Network emulator (NETEM)"
197 help !! 199 ---help---
198 Say Y if you want to emulate network 200 Say Y if you want to emulate network delay, loss, and packet
199 re-ordering. This is often useful to 201 re-ordering. This is often useful to simulate networks when
200 testing applications or protocols. 202 testing applications or protocols.
201 203
202 To compile this driver as a module, 204 To compile this driver as a module, choose M here: the module
203 will be called sch_netem. 205 will be called sch_netem.
204 206
205 If unsure, say N. 207 If unsure, say N.
206 208
207 config NET_SCH_DRR 209 config NET_SCH_DRR
208 tristate "Deficit Round Robin schedule 210 tristate "Deficit Round Robin scheduler (DRR)"
209 help 211 help
210 Say Y here if you want to use the De 212 Say Y here if you want to use the Deficit Round Robin (DRR) packet
211 scheduling algorithm. 213 scheduling algorithm.
212 214
213 To compile this driver as a module, 215 To compile this driver as a module, choose M here: the module
214 will be called sch_drr. 216 will be called sch_drr.
215 217
216 If unsure, say N. 218 If unsure, say N.
217 219
218 config NET_SCH_MQPRIO 220 config NET_SCH_MQPRIO
219 tristate "Multi-queue priority schedul 221 tristate "Multi-queue priority scheduler (MQPRIO)"
220 select NET_SCH_MQPRIO_LIB <<
221 help 222 help
222 Say Y here if you want to use the Mu 223 Say Y here if you want to use the Multi-queue Priority scheduler.
223 This scheduler allows QOS to be offl 224 This scheduler allows QOS to be offloaded on NICs that have support
224 for offloading QOS schedulers. 225 for offloading QOS schedulers.
225 226
226 To compile this driver as a module, 227 To compile this driver as a module, choose M here: the module will
227 be called sch_mqprio. 228 be called sch_mqprio.
228 229
229 If unsure, say N. 230 If unsure, say N.
230 231
231 config NET_SCH_SKBPRIO <<
232 tristate "SKB priority queue scheduler <<
233 help <<
234 Say Y here if you want to use the SK <<
235 scheduler. This schedules packets ac <<
236 which is useful for request packets <<
237 as Gatekeeper. <<
238 <<
239 To compile this driver as a module, <<
240 be called sch_skbprio. <<
241 <<
242 If unsure, say N. <<
243 <<
244 config NET_SCH_CHOKE 232 config NET_SCH_CHOKE
245 tristate "CHOose and Keep responsive f 233 tristate "CHOose and Keep responsive flow scheduler (CHOKE)"
246 help 234 help
247 Say Y here if you want to use the CH 235 Say Y here if you want to use the CHOKe packet scheduler (CHOose
248 and Keep for responsive flows, CHOos 236 and Keep for responsive flows, CHOose and Kill for unresponsive
249 flows). This is a variation of RED w !! 237 flows). This is a variation of RED which trys to penalize flows
250 that monopolize the queue. 238 that monopolize the queue.
251 239
252 To compile this code as a module, ch 240 To compile this code as a module, choose M here: the
253 module will be called sch_choke. 241 module will be called sch_choke.
254 242
255 config NET_SCH_QFQ 243 config NET_SCH_QFQ
256 tristate "Quick Fair Queueing schedule 244 tristate "Quick Fair Queueing scheduler (QFQ)"
257 help 245 help
258 Say Y here if you want to use the Qu 246 Say Y here if you want to use the Quick Fair Queueing Scheduler (QFQ)
259 packet scheduling algorithm. 247 packet scheduling algorithm.
260 248
261 To compile this driver as a module, 249 To compile this driver as a module, choose M here: the module
262 will be called sch_qfq. 250 will be called sch_qfq.
263 251
264 If unsure, say N. 252 If unsure, say N.
265 253
266 config NET_SCH_CODEL 254 config NET_SCH_CODEL
267 tristate "Controlled Delay AQM (CODEL) 255 tristate "Controlled Delay AQM (CODEL)"
268 help 256 help
269 Say Y here if you want to use the Co 257 Say Y here if you want to use the Controlled Delay (CODEL)
270 packet scheduling algorithm. 258 packet scheduling algorithm.
271 259
272 To compile this driver as a module, 260 To compile this driver as a module, choose M here: the module
273 will be called sch_codel. 261 will be called sch_codel.
274 262
275 If unsure, say N. 263 If unsure, say N.
276 264
277 config NET_SCH_FQ_CODEL 265 config NET_SCH_FQ_CODEL
278 tristate "Fair Queue Controlled Delay 266 tristate "Fair Queue Controlled Delay AQM (FQ_CODEL)"
279 help 267 help
280 Say Y here if you want to use the FQ 268 Say Y here if you want to use the FQ Controlled Delay (FQ_CODEL)
281 packet scheduling algorithm. 269 packet scheduling algorithm.
282 270
283 To compile this driver as a module, 271 To compile this driver as a module, choose M here: the module
284 will be called sch_fq_codel. 272 will be called sch_fq_codel.
285 273
286 If unsure, say N. 274 If unsure, say N.
287 275
288 config NET_SCH_CAKE <<
289 tristate "Common Applications Kept Enh <<
290 help <<
291 Say Y here if you want to use the Co <<
292 (CAKE) queue management algorithm. <<
293 <<
294 To compile this driver as a module, <<
295 will be called sch_cake. <<
296 <<
297 If unsure, say N. <<
298 <<
299 config NET_SCH_FQ 276 config NET_SCH_FQ
300 tristate "Fair Queue" 277 tristate "Fair Queue"
301 help 278 help
302 Say Y here if you want to use the FQ 279 Say Y here if you want to use the FQ packet scheduling algorithm.
303 280
304 FQ does flow separation, and is able 281 FQ does flow separation, and is able to respect pacing requirements
305 set by TCP stack into sk->sk_pacing_ !! 282 set by TCP stack into sk->sk_pacing_rate (for localy generated
306 traffic) 283 traffic)
307 284
308 To compile this driver as a module, 285 To compile this driver as a module, choose M here: the module
309 will be called sch_fq. 286 will be called sch_fq.
310 287
311 If unsure, say N. 288 If unsure, say N.
312 289
313 config NET_SCH_HHF 290 config NET_SCH_HHF
314 tristate "Heavy-Hitter Filter (HHF)" 291 tristate "Heavy-Hitter Filter (HHF)"
315 help 292 help
316 Say Y here if you want to use the He 293 Say Y here if you want to use the Heavy-Hitter Filter (HHF)
317 packet scheduling algorithm. 294 packet scheduling algorithm.
318 295
319 To compile this driver as a module, 296 To compile this driver as a module, choose M here: the module
320 will be called sch_hhf. 297 will be called sch_hhf.
321 298
322 config NET_SCH_PIE 299 config NET_SCH_PIE
323 tristate "Proportional Integral contro 300 tristate "Proportional Integral controller Enhanced (PIE) scheduler"
324 help 301 help
325 Say Y here if you want to use the Pr 302 Say Y here if you want to use the Proportional Integral controller
326 Enhanced scheduler packet scheduling 303 Enhanced scheduler packet scheduling algorithm.
327 For more information, please see htt !! 304 For more information, please see
>> 305 http://tools.ietf.org/html/draft-pan-tsvwg-pie-00
328 306
329 To compile this driver as a module, 307 To compile this driver as a module, choose M here: the module
330 will be called sch_pie. 308 will be called sch_pie.
331 309
332 If unsure, say N. 310 If unsure, say N.
333 311
334 config NET_SCH_FQ_PIE <<
335 depends on NET_SCH_PIE <<
336 tristate "Flow Queue Proportional Inte <<
337 help <<
338 Say Y here if you want to use the Fl <<
339 controller Enhanced (FQ-PIE) packet <<
340 For more information, please see htt <<
341 <<
342 To compile this driver as a module, <<
343 will be called sch_fq_pie. <<
344 <<
345 If unsure, say N. <<
346 <<
347 config NET_SCH_INGRESS 312 config NET_SCH_INGRESS
348 tristate "Ingress/classifier-action Qd 313 tristate "Ingress/classifier-action Qdisc"
349 depends on NET_CLS_ACT 314 depends on NET_CLS_ACT
350 select NET_XGRESS !! 315 select NET_INGRESS
351 help !! 316 select NET_EGRESS
>> 317 ---help---
352 Say Y here if you want to use classi 318 Say Y here if you want to use classifiers for incoming and/or outgoing
353 packets. This qdisc doesn't do anyth 319 packets. This qdisc doesn't do anything else besides running classifiers,
354 which can also have actions attached 320 which can also have actions attached to them. In case of outgoing packets,
355 classifiers that this qdisc holds ar 321 classifiers that this qdisc holds are executed in the transmit path
356 before real enqueuing to an egress q 322 before real enqueuing to an egress qdisc happens.
357 323
358 If unsure, say Y. 324 If unsure, say Y.
359 325
360 To compile this code as a module, ch 326 To compile this code as a module, choose M here: the module will be
361 called sch_ingress with alias of sch 327 called sch_ingress with alias of sch_clsact.
362 328
363 config NET_SCH_PLUG 329 config NET_SCH_PLUG
364 tristate "Plug network traffic until r 330 tristate "Plug network traffic until release (PLUG)"
365 help !! 331 ---help---
366 332
367 This queuing discipline allows users 333 This queuing discipline allows userspace to plug/unplug a network
368 output queue, using the netlink inte 334 output queue, using the netlink interface. When it receives an
369 enqueue command it inserts a plug in 335 enqueue command it inserts a plug into the outbound queue that
370 causes following packets to enqueue 336 causes following packets to enqueue until a dequeue command arrives
371 over netlink, causing the plug to be 337 over netlink, causing the plug to be removed and resuming the normal
372 packet flow. 338 packet flow.
373 339
374 This module also provides a generic 340 This module also provides a generic "network output buffering"
375 functionality (aka output commit), w 341 functionality (aka output commit), wherein upon arrival of a dequeue
376 command, only packets up to the firs 342 command, only packets up to the first plug are released for delivery.
377 The Remus HA project uses this modul 343 The Remus HA project uses this module to enable speculative execution
378 of virtual machines by allowing the 344 of virtual machines by allowing the generated network output to be rolled
379 back if needed. 345 back if needed.
380 346
381 For more information, please refer t 347 For more information, please refer to <http://wiki.xenproject.org/wiki/Remus>
382 348
383 Say Y here if you are using this ker 349 Say Y here if you are using this kernel for Xen dom0 and
384 want to protect Xen guests with Remu 350 want to protect Xen guests with Remus.
385 351
386 To compile this code as a module, ch 352 To compile this code as a module, choose M here: the
387 module will be called sch_plug. 353 module will be called sch_plug.
388 354
389 config NET_SCH_ETS <<
390 tristate "Enhanced transmission select <<
391 help <<
392 The Enhanced Transmission Selection <<
393 queuing discipline that merges funct <<
394 qdiscs in one scheduler. ETS makes i <<
395 strict and bandwidth-sharing bands t <<
396 selection described in 802.1Qaz. <<
397 <<
398 Say Y here if you want to use the ET <<
399 algorithm. <<
400 <<
401 To compile this driver as a module, <<
402 will be called sch_ets. <<
403 <<
404 If unsure, say N. <<
405 <<
406 menuconfig NET_SCH_DEFAULT 355 menuconfig NET_SCH_DEFAULT
407 bool "Allow override default queue dis 356 bool "Allow override default queue discipline"
408 help !! 357 ---help---
409 Support for selection of default que 358 Support for selection of default queuing discipline.
410 359
411 Nearly all users can safely say no h 360 Nearly all users can safely say no here, and the default
412 of pfifo_fast will be used. Many dis 361 of pfifo_fast will be used. Many distributions already set
413 the default value via /proc/sys/net/ 362 the default value via /proc/sys/net/core/default_qdisc.
414 363
415 If unsure, say N. 364 If unsure, say N.
416 365
417 if NET_SCH_DEFAULT 366 if NET_SCH_DEFAULT
418 367
419 choice 368 choice
420 prompt "Default queuing discipline" 369 prompt "Default queuing discipline"
421 default DEFAULT_PFIFO_FAST 370 default DEFAULT_PFIFO_FAST
422 help 371 help
423 Select the queueing discipline that 372 Select the queueing discipline that will be used by default
424 for all network devices. 373 for all network devices.
425 374
426 config DEFAULT_FQ 375 config DEFAULT_FQ
427 bool "Fair Queue" if NET_SCH_F 376 bool "Fair Queue" if NET_SCH_FQ
428 377
429 config DEFAULT_CODEL 378 config DEFAULT_CODEL
430 bool "Controlled Delay" if NET 379 bool "Controlled Delay" if NET_SCH_CODEL
431 380
432 config DEFAULT_FQ_CODEL 381 config DEFAULT_FQ_CODEL
433 bool "Fair Queue Controlled De 382 bool "Fair Queue Controlled Delay" if NET_SCH_FQ_CODEL
434 383
435 config DEFAULT_FQ_PIE <<
436 bool "Flow Queue Proportional <<
437 <<
438 config DEFAULT_SFQ 384 config DEFAULT_SFQ
439 bool "Stochastic Fair Queue" i 385 bool "Stochastic Fair Queue" if NET_SCH_SFQ
440 386
441 config DEFAULT_PFIFO_FAST 387 config DEFAULT_PFIFO_FAST
442 bool "Priority FIFO Fast" 388 bool "Priority FIFO Fast"
443 endchoice 389 endchoice
444 390
445 config DEFAULT_NET_SCH 391 config DEFAULT_NET_SCH
446 string 392 string
447 default "pfifo_fast" if DEFAULT_PFIFO_ 393 default "pfifo_fast" if DEFAULT_PFIFO_FAST
448 default "fq" if DEFAULT_FQ 394 default "fq" if DEFAULT_FQ
449 default "fq_codel" if DEFAULT_FQ_CODEL 395 default "fq_codel" if DEFAULT_FQ_CODEL
450 default "fq_pie" if DEFAULT_FQ_PIE <<
451 default "sfq" if DEFAULT_SFQ 396 default "sfq" if DEFAULT_SFQ
452 default "pfifo_fast" 397 default "pfifo_fast"
453 endif 398 endif
454 399
455 comment "Classification" 400 comment "Classification"
456 401
457 config NET_CLS 402 config NET_CLS
458 bool 403 bool
459 404
460 config NET_CLS_BASIC 405 config NET_CLS_BASIC
461 tristate "Elementary classification (B 406 tristate "Elementary classification (BASIC)"
462 select NET_CLS 407 select NET_CLS
463 help !! 408 ---help---
464 Say Y here if you want to be able to 409 Say Y here if you want to be able to classify packets using
465 only extended matches and actions. 410 only extended matches and actions.
466 411
467 To compile this code as a module, ch 412 To compile this code as a module, choose M here: the
468 module will be called cls_basic. 413 module will be called cls_basic.
469 414
>> 415 config NET_CLS_TCINDEX
>> 416 tristate "Traffic-Control Index (TCINDEX)"
>> 417 select NET_CLS
>> 418 ---help---
>> 419 Say Y here if you want to be able to classify packets based on
>> 420 traffic control indices. You will want this feature if you want
>> 421 to implement Differentiated Services together with DSMARK.
>> 422
>> 423 To compile this code as a module, choose M here: the
>> 424 module will be called cls_tcindex.
>> 425
470 config NET_CLS_ROUTE4 426 config NET_CLS_ROUTE4
471 tristate "Routing decision (ROUTE)" 427 tristate "Routing decision (ROUTE)"
472 depends on INET 428 depends on INET
473 select IP_ROUTE_CLASSID 429 select IP_ROUTE_CLASSID
474 select NET_CLS 430 select NET_CLS
475 help !! 431 ---help---
476 If you say Y here, you will be able 432 If you say Y here, you will be able to classify packets
477 according to the route table entry t 433 according to the route table entry they matched.
478 434
479 To compile this code as a module, ch 435 To compile this code as a module, choose M here: the
480 module will be called cls_route. 436 module will be called cls_route.
481 437
482 config NET_CLS_FW 438 config NET_CLS_FW
483 tristate "Netfilter mark (FW)" 439 tristate "Netfilter mark (FW)"
484 select NET_CLS 440 select NET_CLS
485 help !! 441 ---help---
486 If you say Y here, you will be able 442 If you say Y here, you will be able to classify packets
487 according to netfilter/firewall mark 443 according to netfilter/firewall marks.
488 444
489 To compile this code as a module, ch 445 To compile this code as a module, choose M here: the
490 module will be called cls_fw. 446 module will be called cls_fw.
491 447
492 config NET_CLS_U32 448 config NET_CLS_U32
493 tristate "Universal 32bit comparisons 449 tristate "Universal 32bit comparisons w/ hashing (U32)"
494 select NET_CLS 450 select NET_CLS
495 help !! 451 ---help---
496 Say Y here to be able to classify pa 452 Say Y here to be able to classify packets using a universal
497 32bit pieces based comparison scheme 453 32bit pieces based comparison scheme.
498 454
499 To compile this code as a module, ch 455 To compile this code as a module, choose M here: the
500 module will be called cls_u32. 456 module will be called cls_u32.
501 457
502 config CLS_U32_PERF 458 config CLS_U32_PERF
503 bool "Performance counters support" 459 bool "Performance counters support"
504 depends on NET_CLS_U32 460 depends on NET_CLS_U32
505 help !! 461 ---help---
506 Say Y here to make u32 gather additi 462 Say Y here to make u32 gather additional statistics useful for
507 fine tuning u32 classifiers. 463 fine tuning u32 classifiers.
508 464
509 config CLS_U32_MARK 465 config CLS_U32_MARK
510 bool "Netfilter marks support" 466 bool "Netfilter marks support"
511 depends on NET_CLS_U32 467 depends on NET_CLS_U32
512 help !! 468 ---help---
513 Say Y here to be able to use netfilt 469 Say Y here to be able to use netfilter marks as u32 key.
514 470
>> 471 config NET_CLS_RSVP
>> 472 tristate "IPv4 Resource Reservation Protocol (RSVP)"
>> 473 select NET_CLS
>> 474 ---help---
>> 475 The Resource Reservation Protocol (RSVP) permits end systems to
>> 476 request a minimum and maximum data flow rate for a connection; this
>> 477 is important for real time data such as streaming sound or video.
>> 478
>> 479 Say Y here if you want to be able to classify outgoing packets based
>> 480 on their RSVP requests.
>> 481
>> 482 To compile this code as a module, choose M here: the
>> 483 module will be called cls_rsvp.
>> 484
>> 485 config NET_CLS_RSVP6
>> 486 tristate "IPv6 Resource Reservation Protocol (RSVP6)"
>> 487 select NET_CLS
>> 488 ---help---
>> 489 The Resource Reservation Protocol (RSVP) permits end systems to
>> 490 request a minimum and maximum data flow rate for a connection; this
>> 491 is important for real time data such as streaming sound or video.
>> 492
>> 493 Say Y here if you want to be able to classify outgoing packets based
>> 494 on their RSVP requests and you are using the IPv6 protocol.
>> 495
>> 496 To compile this code as a module, choose M here: the
>> 497 module will be called cls_rsvp6.
>> 498
515 config NET_CLS_FLOW 499 config NET_CLS_FLOW
516 tristate "Flow classifier" 500 tristate "Flow classifier"
517 select NET_CLS 501 select NET_CLS
518 help !! 502 ---help---
519 If you say Y here, you will be able 503 If you say Y here, you will be able to classify packets based on
520 a configurable combination of packet 504 a configurable combination of packet keys. This is mostly useful
521 in combination with SFQ. 505 in combination with SFQ.
522 506
523 To compile this code as a module, ch 507 To compile this code as a module, choose M here: the
524 module will be called cls_flow. 508 module will be called cls_flow.
525 509
526 config NET_CLS_CGROUP 510 config NET_CLS_CGROUP
527 tristate "Control Group Classifier" 511 tristate "Control Group Classifier"
528 select NET_CLS 512 select NET_CLS
529 select CGROUP_NET_CLASSID 513 select CGROUP_NET_CLASSID
530 depends on CGROUPS 514 depends on CGROUPS
531 help !! 515 ---help---
532 Say Y here if you want to classify p 516 Say Y here if you want to classify packets based on the control
533 cgroup of their process. 517 cgroup of their process.
534 518
535 To compile this code as a module, ch 519 To compile this code as a module, choose M here: the
536 module will be called cls_cgroup. 520 module will be called cls_cgroup.
537 521
538 config NET_CLS_BPF 522 config NET_CLS_BPF
539 tristate "BPF-based classifier" 523 tristate "BPF-based classifier"
540 select NET_CLS 524 select NET_CLS
541 help !! 525 ---help---
542 If you say Y here, you will be able 526 If you say Y here, you will be able to classify packets based on
543 programmable BPF (JIT'ed) filters as 527 programmable BPF (JIT'ed) filters as an alternative to ematches.
544 528
545 To compile this code as a module, ch 529 To compile this code as a module, choose M here: the module will
546 be called cls_bpf. 530 be called cls_bpf.
547 531
548 config NET_CLS_FLOWER 532 config NET_CLS_FLOWER
549 tristate "Flower classifier" 533 tristate "Flower classifier"
550 select NET_CLS 534 select NET_CLS
551 help !! 535 ---help---
552 If you say Y here, you will be able 536 If you say Y here, you will be able to classify packets based on
553 a configurable combination of packet 537 a configurable combination of packet keys and masks.
554 538
555 To compile this code as a module, ch 539 To compile this code as a module, choose M here: the module will
556 be called cls_flower. 540 be called cls_flower.
557 541
558 config NET_CLS_MATCHALL 542 config NET_CLS_MATCHALL
559 tristate "Match-all classifier" 543 tristate "Match-all classifier"
560 select NET_CLS 544 select NET_CLS
561 help !! 545 ---help---
562 If you say Y here, you will be able 546 If you say Y here, you will be able to classify packets based on
563 nothing. Every packet will match. 547 nothing. Every packet will match.
564 548
565 To compile this code as a module, ch 549 To compile this code as a module, choose M here: the module will
566 be called cls_matchall. 550 be called cls_matchall.
567 551
568 config NET_EMATCH 552 config NET_EMATCH
569 bool "Extended Matches" 553 bool "Extended Matches"
570 select NET_CLS 554 select NET_CLS
571 help !! 555 ---help---
572 Say Y here if you want to use extend 556 Say Y here if you want to use extended matches on top of classifiers
573 and select the extended matches belo 557 and select the extended matches below.
574 558
575 Extended matches are small classific 559 Extended matches are small classification helpers not worth writing
576 a separate classifier for. 560 a separate classifier for.
577 561
578 A recent version of the iproute2 pac 562 A recent version of the iproute2 package is required to use
579 extended matches. 563 extended matches.
580 564
581 config NET_EMATCH_STACK 565 config NET_EMATCH_STACK
582 int "Stack size" 566 int "Stack size"
583 depends on NET_EMATCH 567 depends on NET_EMATCH
584 default "32" 568 default "32"
585 help !! 569 ---help---
586 Size of the local stack variable use 570 Size of the local stack variable used while evaluating the tree of
587 ematches. Limits the depth of the tr 571 ematches. Limits the depth of the tree, i.e. the number of
588 encapsulated precedences. Every leve 572 encapsulated precedences. Every level requires 4 bytes of additional
589 stack space. 573 stack space.
590 574
591 config NET_EMATCH_CMP 575 config NET_EMATCH_CMP
592 tristate "Simple packet data compariso 576 tristate "Simple packet data comparison"
593 depends on NET_EMATCH 577 depends on NET_EMATCH
594 help !! 578 ---help---
595 Say Y here if you want to be able to 579 Say Y here if you want to be able to classify packets based on
596 simple packet data comparisons for 8 580 simple packet data comparisons for 8, 16, and 32bit values.
597 581
598 To compile this code as a module, ch 582 To compile this code as a module, choose M here: the
599 module will be called em_cmp. 583 module will be called em_cmp.
600 584
601 config NET_EMATCH_NBYTE 585 config NET_EMATCH_NBYTE
602 tristate "Multi byte comparison" 586 tristate "Multi byte comparison"
603 depends on NET_EMATCH 587 depends on NET_EMATCH
604 help !! 588 ---help---
605 Say Y here if you want to be able to 589 Say Y here if you want to be able to classify packets based on
606 multiple byte comparisons mainly use 590 multiple byte comparisons mainly useful for IPv6 address comparisons.
607 591
608 To compile this code as a module, ch 592 To compile this code as a module, choose M here: the
609 module will be called em_nbyte. 593 module will be called em_nbyte.
610 594
611 config NET_EMATCH_U32 595 config NET_EMATCH_U32
612 tristate "U32 key" 596 tristate "U32 key"
613 depends on NET_EMATCH 597 depends on NET_EMATCH
614 help !! 598 ---help---
615 Say Y here if you want to be able to 599 Say Y here if you want to be able to classify packets using
616 the famous u32 key in combination wi 600 the famous u32 key in combination with logic relations.
617 601
618 To compile this code as a module, ch 602 To compile this code as a module, choose M here: the
619 module will be called em_u32. 603 module will be called em_u32.
620 604
621 config NET_EMATCH_META 605 config NET_EMATCH_META
622 tristate "Metadata" 606 tristate "Metadata"
623 depends on NET_EMATCH 607 depends on NET_EMATCH
624 help !! 608 ---help---
625 Say Y here if you want to be able to 609 Say Y here if you want to be able to classify packets based on
626 metadata such as load average, netfi 610 metadata such as load average, netfilter attributes, socket
627 attributes and routing decisions. 611 attributes and routing decisions.
628 612
629 To compile this code as a module, ch 613 To compile this code as a module, choose M here: the
630 module will be called em_meta. 614 module will be called em_meta.
631 615
632 config NET_EMATCH_TEXT 616 config NET_EMATCH_TEXT
633 tristate "Textsearch" 617 tristate "Textsearch"
634 depends on NET_EMATCH 618 depends on NET_EMATCH
635 select TEXTSEARCH 619 select TEXTSEARCH
636 select TEXTSEARCH_KMP 620 select TEXTSEARCH_KMP
637 select TEXTSEARCH_BM 621 select TEXTSEARCH_BM
638 select TEXTSEARCH_FSM 622 select TEXTSEARCH_FSM
639 help !! 623 ---help---
640 Say Y here if you want to be able to 624 Say Y here if you want to be able to classify packets based on
641 textsearch comparisons. 625 textsearch comparisons.
642 626
643 To compile this code as a module, ch 627 To compile this code as a module, choose M here: the
644 module will be called em_text. 628 module will be called em_text.
645 629
646 config NET_EMATCH_CANID 630 config NET_EMATCH_CANID
647 tristate "CAN Identifier" 631 tristate "CAN Identifier"
648 depends on NET_EMATCH && (CAN=y || CAN 632 depends on NET_EMATCH && (CAN=y || CAN=m)
649 help !! 633 ---help---
650 Say Y here if you want to be able to 634 Say Y here if you want to be able to classify CAN frames based
651 on CAN Identifier. 635 on CAN Identifier.
652 636
653 To compile this code as a module, ch 637 To compile this code as a module, choose M here: the
654 module will be called em_canid. 638 module will be called em_canid.
655 639
656 config NET_EMATCH_IPSET 640 config NET_EMATCH_IPSET
657 tristate "IPset" 641 tristate "IPset"
658 depends on NET_EMATCH && IP_SET 642 depends on NET_EMATCH && IP_SET
659 help !! 643 ---help---
660 Say Y here if you want to be able to 644 Say Y here if you want to be able to classify packets based on
661 ipset membership. 645 ipset membership.
662 646
663 To compile this code as a module, ch 647 To compile this code as a module, choose M here: the
664 module will be called em_ipset. 648 module will be called em_ipset.
665 649
666 config NET_EMATCH_IPT <<
667 tristate "IPtables Matches" <<
668 depends on NET_EMATCH && NETFILTER && <<
669 help <<
670 Say Y here to be able to classify pa <<
671 matches. <<
672 Current supported match is "policy" <<
673 based on IPsec policy that was used <<
674 <<
675 To compile this code as a module, ch <<
676 module will be called em_ipt. <<
677 <<
678 config NET_CLS_ACT 650 config NET_CLS_ACT
679 bool "Actions" 651 bool "Actions"
680 select NET_CLS 652 select NET_CLS
681 select NET_XGRESS !! 653 ---help---
682 help <<
683 Say Y here if you want to use traffi 654 Say Y here if you want to use traffic control actions. Actions
684 get attached to classifiers and are 655 get attached to classifiers and are invoked after a successful
685 classification. They are used to ove 656 classification. They are used to overwrite the classification
686 result, instantly drop or redirect p 657 result, instantly drop or redirect packets, etc.
687 658
688 A recent version of the iproute2 pac 659 A recent version of the iproute2 package is required to use
689 extended matches. 660 extended matches.
690 661
691 config NET_ACT_POLICE 662 config NET_ACT_POLICE
692 tristate "Traffic Policing" 663 tristate "Traffic Policing"
693 depends on NET_CLS_ACT !! 664 depends on NET_CLS_ACT
694 help !! 665 ---help---
695 Say Y here if you want to do traffic 666 Say Y here if you want to do traffic policing, i.e. strict
696 bandwidth limiting. This action repl 667 bandwidth limiting. This action replaces the existing policing
697 module. 668 module.
698 669
699 To compile this code as a module, ch 670 To compile this code as a module, choose M here: the
700 module will be called act_police. 671 module will be called act_police.
701 672
702 config NET_ACT_GACT 673 config NET_ACT_GACT
703 tristate "Generic actions" !! 674 tristate "Generic actions"
704 depends on NET_CLS_ACT !! 675 depends on NET_CLS_ACT
705 help !! 676 ---help---
706 Say Y here to take generic actions s 677 Say Y here to take generic actions such as dropping and
707 accepting packets. 678 accepting packets.
708 679
709 To compile this code as a module, ch 680 To compile this code as a module, choose M here: the
710 module will be called act_gact. 681 module will be called act_gact.
711 682
712 config GACT_PROB 683 config GACT_PROB
713 bool "Probability support" !! 684 bool "Probability support"
714 depends on NET_ACT_GACT !! 685 depends on NET_ACT_GACT
715 help !! 686 ---help---
716 Say Y here to use the generic action 687 Say Y here to use the generic action randomly or deterministically.
717 688
718 config NET_ACT_MIRRED 689 config NET_ACT_MIRRED
719 tristate "Redirecting and Mirroring" !! 690 tristate "Redirecting and Mirroring"
720 depends on NET_CLS_ACT !! 691 depends on NET_CLS_ACT
721 help !! 692 ---help---
722 Say Y here to allow packets to be mi 693 Say Y here to allow packets to be mirrored or redirected to
723 other devices. 694 other devices.
724 695
725 To compile this code as a module, ch 696 To compile this code as a module, choose M here: the
726 module will be called act_mirred. 697 module will be called act_mirred.
727 698
728 config NET_ACT_SAMPLE 699 config NET_ACT_SAMPLE
729 tristate "Traffic Sampling" !! 700 tristate "Traffic Sampling"
730 depends on NET_CLS_ACT !! 701 depends on NET_CLS_ACT
731 select PSAMPLE !! 702 select PSAMPLE
732 help !! 703 ---help---
733 Say Y here to allow packet sampling 704 Say Y here to allow packet sampling tc action. The packet sample
734 action consists of statistically cho 705 action consists of statistically choosing packets and sampling
735 them using the psample module. 706 them using the psample module.
736 707
737 To compile this code as a module, ch 708 To compile this code as a module, choose M here: the
738 module will be called act_sample. 709 module will be called act_sample.
739 710
>> 711 config NET_ACT_IPT
>> 712 tristate "IPtables targets"
>> 713 depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES
>> 714 ---help---
>> 715 Say Y here to be able to invoke iptables targets after successful
>> 716 classification.
>> 717
>> 718 To compile this code as a module, choose M here: the
>> 719 module will be called act_ipt.
>> 720
740 config NET_ACT_NAT 721 config NET_ACT_NAT
741 tristate "Stateless NAT" !! 722 tristate "Stateless NAT"
742 depends on NET_CLS_ACT !! 723 depends on NET_CLS_ACT
743 help !! 724 ---help---
744 Say Y here to do stateless NAT on IP 725 Say Y here to do stateless NAT on IPv4 packets. You should use
745 netfilter for NAT unless you know wh 726 netfilter for NAT unless you know what you are doing.
746 727
747 To compile this code as a module, ch 728 To compile this code as a module, choose M here: the
748 module will be called act_nat. 729 module will be called act_nat.
749 730
750 config NET_ACT_PEDIT 731 config NET_ACT_PEDIT
751 tristate "Packet Editing" !! 732 tristate "Packet Editing"
752 depends on NET_CLS_ACT !! 733 depends on NET_CLS_ACT
753 help !! 734 ---help---
754 Say Y here if you want to mangle the 735 Say Y here if you want to mangle the content of packets.
755 736
756 To compile this code as a module, ch 737 To compile this code as a module, choose M here: the
757 module will be called act_pedit. 738 module will be called act_pedit.
758 739
759 config NET_ACT_SIMP 740 config NET_ACT_SIMP
760 tristate "Simple Example (Debug)" !! 741 tristate "Simple Example (Debug)"
761 depends on NET_CLS_ACT !! 742 depends on NET_CLS_ACT
762 help !! 743 ---help---
763 Say Y here to add a simple action fo 744 Say Y here to add a simple action for demonstration purposes.
764 It is meant as an example and for de 745 It is meant as an example and for debugging purposes. It will
765 print a configured policy string fol 746 print a configured policy string followed by the packet count
766 to the console for every packet that 747 to the console for every packet that passes by.
767 748
768 If unsure, say N. 749 If unsure, say N.
769 750
770 To compile this code as a module, ch 751 To compile this code as a module, choose M here: the
771 module will be called act_simple. 752 module will be called act_simple.
772 753
773 config NET_ACT_SKBEDIT 754 config NET_ACT_SKBEDIT
774 tristate "SKB Editing" !! 755 tristate "SKB Editing"
775 depends on NET_CLS_ACT !! 756 depends on NET_CLS_ACT
776 help !! 757 ---help---
777 Say Y here to change skb priority or 758 Say Y here to change skb priority or queue_mapping settings.
778 759
779 If unsure, say N. 760 If unsure, say N.
780 761
781 To compile this code as a module, ch 762 To compile this code as a module, choose M here: the
782 module will be called act_skbedit. 763 module will be called act_skbedit.
783 764
784 config NET_ACT_CSUM 765 config NET_ACT_CSUM
785 tristate "Checksum Updating" !! 766 tristate "Checksum Updating"
786 depends on NET_CLS_ACT && INET !! 767 depends on NET_CLS_ACT && INET
787 select LIBCRC32C !! 768 select LIBCRC32C
788 help !! 769 ---help---
789 Say Y here to update some common che 770 Say Y here to update some common checksum after some direct
790 packet alterations. 771 packet alterations.
791 772
792 To compile this code as a module, ch 773 To compile this code as a module, choose M here: the
793 module will be called act_csum. 774 module will be called act_csum.
794 775
795 config NET_ACT_MPLS <<
796 tristate "MPLS manipulation" <<
797 depends on NET_CLS_ACT <<
798 help <<
799 Say Y here to push or pop MPLS heade <<
800 <<
801 If unsure, say N. <<
802 <<
803 To compile this code as a module, ch <<
804 module will be called act_mpls. <<
805 <<
806 config NET_ACT_VLAN 776 config NET_ACT_VLAN
807 tristate "Vlan manipulation" !! 777 tristate "Vlan manipulation"
808 depends on NET_CLS_ACT !! 778 depends on NET_CLS_ACT
809 help !! 779 ---help---
810 Say Y here to push or pop vlan heade 780 Say Y here to push or pop vlan headers.
811 781
812 If unsure, say N. 782 If unsure, say N.
813 783
814 To compile this code as a module, ch 784 To compile this code as a module, choose M here: the
815 module will be called act_vlan. 785 module will be called act_vlan.
816 786
817 config NET_ACT_BPF 787 config NET_ACT_BPF
818 tristate "BPF based action" !! 788 tristate "BPF based action"
819 depends on NET_CLS_ACT !! 789 depends on NET_CLS_ACT
820 help !! 790 ---help---
821 Say Y here to execute BPF code on pa 791 Say Y here to execute BPF code on packets. The BPF code will decide
822 if the packet should be dropped or n 792 if the packet should be dropped or not.
823 793
824 If unsure, say N. 794 If unsure, say N.
825 795
826 To compile this code as a module, ch 796 To compile this code as a module, choose M here: the
827 module will be called act_bpf. 797 module will be called act_bpf.
828 798
829 config NET_ACT_CONNMARK 799 config NET_ACT_CONNMARK
830 tristate "Netfilter Connection Mark Re !! 800 tristate "Netfilter Connection Mark Retriever"
831 depends on NET_CLS_ACT && NETFILTER !! 801 depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES
832 depends on NF_CONNTRACK && NF_CONNTRAC !! 802 depends on NF_CONNTRACK && NF_CONNTRACK_MARK
833 help !! 803 ---help---
834 Say Y here to allow retrieving of co 804 Say Y here to allow retrieving of conn mark
835 805
836 If unsure, say N. 806 If unsure, say N.
837 807
838 To compile this code as a module, ch 808 To compile this code as a module, choose M here: the
839 module will be called act_connmark. 809 module will be called act_connmark.
840 810
841 config NET_ACT_CTINFO <<
842 tristate "Netfilter Connection Mark Ac <<
843 depends on NET_CLS_ACT && NETFILTER <<
844 depends on NF_CONNTRACK && NF_CONNTRAC <<
845 help <<
846 Say Y here to allow transfer of a co <<
847 Current actions transfer connmark st <<
848 ipv4/v6 diffserv and/or to transfer <<
849 mark. Both are useful for restoring <<
850 back onto ingress connections for qd <<
851 purposes. <<
852 <<
853 If unsure, say N. <<
854 <<
855 To compile this code as a module, ch <<
856 module will be called act_ctinfo. <<
857 <<
858 config NET_ACT_SKBMOD 811 config NET_ACT_SKBMOD
859 tristate "skb data modification action !! 812 tristate "skb data modification action"
860 depends on NET_CLS_ACT !! 813 depends on NET_CLS_ACT
861 help !! 814 ---help---
862 Say Y here to allow modification of s !! 815 Say Y here to allow modification of skb data
863 816
864 If unsure, say N. !! 817 If unsure, say N.
865 818
866 To compile this code as a module, cho !! 819 To compile this code as a module, choose M here: the
867 module will be called act_skbmod. !! 820 module will be called act_skbmod.
868 821
869 config NET_ACT_IFE 822 config NET_ACT_IFE
870 tristate "Inter-FE action based on IET !! 823 tristate "Inter-FE action based on IETF ForCES InterFE LFB"
871 depends on NET_CLS_ACT !! 824 depends on NET_CLS_ACT
872 select NET_IFE !! 825 select NET_IFE
873 help !! 826 ---help---
874 Say Y here to allow for sourcing and 827 Say Y here to allow for sourcing and terminating metadata
875 For details refer to netdev01 paper: 828 For details refer to netdev01 paper:
876 "Distributing Linux Traffic Control 829 "Distributing Linux Traffic Control Classifier-Action Subsystem"
877 Authors: Jamal Hadi Salim and Damas 830 Authors: Jamal Hadi Salim and Damascene M. Joachimpillai
878 831
879 To compile this code as a module, ch 832 To compile this code as a module, choose M here: the
880 module will be called act_ife. 833 module will be called act_ife.
881 834
882 config NET_ACT_TUNNEL_KEY 835 config NET_ACT_TUNNEL_KEY
883 tristate "IP tunnel metadata manipulat !! 836 tristate "IP tunnel metadata manipulation"
884 depends on NET_CLS_ACT !! 837 depends on NET_CLS_ACT
885 help !! 838 ---help---
886 Say Y here to set/release ip tunnel 839 Say Y here to set/release ip tunnel metadata.
887 840
888 If unsure, say N. 841 If unsure, say N.
889 842
890 To compile this code as a module, ch 843 To compile this code as a module, choose M here: the
891 module will be called act_tunnel_key 844 module will be called act_tunnel_key.
892 845
893 config NET_ACT_CT <<
894 tristate "connection tracking tc actio <<
895 depends on NET_CLS_ACT && NF_CONNTRACK <<
896 select NF_CONNTRACK_OVS <<
897 select NF_NAT_OVS if NF_NAT <<
898 help <<
899 Say Y here to allow sending the pack <<
900 <<
901 If unsure, say N. <<
902 <<
903 To compile this code as a module, ch <<
904 module will be called act_ct. <<
905 <<
906 config NET_ACT_GATE <<
907 tristate "Frame gate entry list contro <<
908 depends on NET_CLS_ACT <<
909 help <<
910 Say Y here to allow to control the i <<
911 specific time slot and be dropped at <<
912 the gate entry list. <<
913 <<
914 If unsure, say N. <<
915 To compile this code as a module, ch <<
916 module will be called act_gate. <<
917 <<
918 config NET_IFE_SKBMARK 846 config NET_IFE_SKBMARK
919 tristate "Support to encoding decoding !! 847 tristate "Support to encoding decoding skb mark on IFE action"
920 depends on NET_ACT_IFE !! 848 depends on NET_ACT_IFE
>> 849 ---help---
921 850
922 config NET_IFE_SKBPRIO 851 config NET_IFE_SKBPRIO
923 tristate "Support to encoding decoding !! 852 tristate "Support to encoding decoding skb prio on IFE action"
924 depends on NET_ACT_IFE !! 853 depends on NET_ACT_IFE
>> 854 ---help---
925 855
926 config NET_IFE_SKBTCINDEX 856 config NET_IFE_SKBTCINDEX
927 tristate "Support to encoding decoding !! 857 tristate "Support to encoding decoding skb tcindex on IFE action"
928 depends on NET_ACT_IFE !! 858 depends on NET_ACT_IFE
929 !! 859 ---help---
930 config NET_TC_SKB_EXT !! 860
931 bool "TC recirculation support" !! 861 config NET_CLS_IND
932 depends on NET_CLS_ACT !! 862 bool "Incoming device classification"
933 select SKB_EXTENSIONS !! 863 depends on NET_CLS_U32 || NET_CLS_FW
934 !! 864 ---help---
935 help !! 865 Say Y here to extend the u32 and fw classifier to support
936 Say Y here to allow tc chain misses !! 866 classification based on the incoming device. This option is
937 the correct recirc_id, and hardware !! 867 likely to disappear in favour of the metadata ematch.
938 the correct chain in tc software dat <<
939 <<
940 Say N here if you won't be using tc< <<
941 868
942 endif # NET_SCHED 869 endif # NET_SCHED
943 870
944 config NET_SCH_FIFO 871 config NET_SCH_FIFO
945 bool 872 bool
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.