| /linux/Documentation/translations/zh_CN/process/ |
| H A D | index.rst | 27 license-rules
65 stable-kernel-rules
|
| H A D | license-rules.rst | 5 :Original: :ref:`Documentation/process/license-rules.rst <kernel_licensing>`
187 guidelines in the licensing rules documentation.
202 guidelines in the licensing rules documentation.
242 guidelines in the licensing rules documentation.
|
| H A D | howto.rst | 67 :ref:`Documentation/translations/zh_CN/process/license-rules.rst <cn_kernel_licensing>`
138 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
270 内核源码中的 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
|
| /linux/Documentation/userspace-api/ |
| H A D | landlock.rst | 29 Landlock rules
33 perform. A set of rules is aggregated in a ruleset, which can then restrict
36 The two existing types of rules are:
38 Filesystem rules
39 For these rules, the object is a file hierarchy,
43 Network rules (since ABI v4)
44 For these rules, the object is a TCP port,
50 We first need to define the ruleset that will contain our rules.
52 For this example, the ruleset will contain rules that only allow filesystem
124 This enables to create an inclusive ruleset that will contain our rules.
[all …]
|
| /linux/Documentation/process/ |
| H A D | index.rst | 55 These are the rules that we try to live by in the kernel community (and
61 license-rules
68 stable-kernel-rules
|
| /linux/Documentation/networking/ |
| H A D | tc-actions-env-rules.rst | 8 The "environmental" rules for authors of any new tc actions are:
23 The "environmental" rules for callers of actions (qdiscs etc) are:
|
| H A D | representors.rst | 69 fast-path rules in the virtual switch. Packets transmitted on the
77 3. It acts as a handle by which switching rules (such as TC filters) can refer
78 to the representee, allowing these rules to be offloaded.
115 representor TC rules.
133 access that the IP stack "sees" would then be configurable through tc rules;
175 It is expected that userland will use this information (e.g. through udev rules)
183 How do representors interact with TC rules?
197 ``REP_DEV`` is a VF representor, the following rules::
213 Of course the rules can (if supported by the NIC) include packet-modifying
220 function uplink netdev or port representor). TC rules such as::
[all …]
|
| H A D | vrf.rst | 10 The VRF device combined with ip rules provides the ability to create virtual
21 the use of higher priority ip rules (Policy Based Routing, PBR) to take
22 precedence over the VRF device rules directing specific traffic as desired.
48 flow through the VRF device. Similarly on egress routing rules are used to
51 and out of the VRF as a whole\ [1]_. Similarly, netfilter\ [2]_ and tc rules
52 can be applied using the VRF device to specify rules that apply to the VRF
60 ingress device and both INPUT and PREROUTING rules with skb->dev set to
61 the VRF device. For egress POSTROUTING and OUTPUT rules can be written
76 with a different priority or install per-VRF rules.
78 Prior to the v4.8 kernel iif and oif rules are needed for each VRF device::
[all …]
|
| /linux/Documentation/translations/ja_JP/ |
| H A D | stable_kernel_rules.txt | 2 This is Japanese translated version of "Documentation/process/stable-kernel-rules.rst".
15 linux-2.6.29/Documentation/process/stable-kernel-rules.rst
|
| /linux/Documentation/arch/arm/ |
| H A D | kernel_mode_neon.rst | 55 following rules and restrictions apply in the kernel:
89 kernel is by adhering to the following rules:
104 NEON assembler is supported with no additional caveats as long as the rules
112 supported as long as the rules above are followed.
119 observe the following in addition to the rules above:
|
| /linux/drivers/net/ethernet/mellanox/mlx5/core/ |
| H A D | Kconfig | 53 flow rules to direct traffic into arbitrary rx queue via ethtool set/get_rxnfc
84 offloading rules for traffic between such ports. Supports VLANs (trunk and
107 Say Y here if you want to support offloading connection tracking rules
118 Say Y here if you want to support offloading sample rules via tc
120 If set to N, will not be able to configure tc rules with sample
|
| /linux/security/integrity/ima/ |
| H A D | Kconfig | 61 Disabling this option will disregard LSM based policy rules.
129 IMA policy can now be updated multiple times. The new rules get
130 appended to the original policy. Have in mind that the rules are
142 This option allows the root user to see the current policy rules.
168 bool "IMA build time configured policy rules"
175 policy rules persist after loading a custom policy.
177 Depending on the rules configured, this policy may require kernel
|
| /linux/Documentation/translations/zh_CN/mm/ |
| H A D | page_owner.rst | 114 --cull <rules>
117 <rules>是一个以逗号分隔的列表形式的单一参数，它提供了一种指定单个剔除规则的
|
| /linux/Documentation/networking/device_drivers/ethernet/aquantia/ |
| H A D | atlantic.rst | 256 RX flow rules (ntuple filters)
259 There are separate rules supported, that applies in that order:
261 1. 16 VLAN ID rules
262 2. 16 L2 EtherType rules
263 3. 8 L3/L4 5-Tuple rules
269 To enable or disable the RX flow rules::
277 Because of the fixed order of the rules, the location of filters is also fixed:
299 For ``flow-type ip4|udp4|tcp4|sctp4|ip6|udp6|tcp6|sctp6`` you can set 8 rules
300 for traffic IPv4 or you can set 2 rules for traffic IPv6. Loc number traffic
|
| /linux/tools/testing/selftests/powerpc/nx-gzip/ |
| H A D | README | 10 /etc/udev/rules.d/99-nx-gzip.rules
|
| /linux/drivers/net/dsa/sja1105/ |
| H A D | sja1105_flower.c | 12 list_for_each_entry(rule, &priv->flow_block.rules, list) in sja1105_rule_find()
94 list_add(&rule->list, &priv->flow_block.rules); in sja1105_setup_bcast_policer()
166 list_add(&rule->list, &priv->flow_block.rules); in sja1105_setup_tc_policer()
528 INIT_LIST_HEAD(&priv->flow_block.rules); in sja1105_flower_setup()
540 list_for_each_safe(pos, n, &priv->flow_block.rules) { in sja1105_flower_teardown()
|
| H A D | sja1105_vl.c | 102 list_for_each_entry(rule, &priv->flow_block.rules, list) { in sja1105_compose_gating_subschedule()
124 list_for_each_entry(rule, &priv->flow_block.rules, list) { in sja1105_compose_gating_subschedule()
326 list_for_each_entry(rule, &priv->flow_block.rules, list) { in sja1105_init_virtual_links()
396 list_for_each_entry(rule, &priv->flow_block.rules, list) { in sja1105_init_virtual_links()
534 list_add(&rule->list, &priv->flow_block.rules); in sja1105_vl_redirect()
629 list_add(&rule->list, &priv->flow_block.rules); in sja1105_vl_gate()
|
| /linux/Documentation/mm/ |
| H A D | page_owner.rst | 175 --cull <rules>
176 Specify culling rules.Culling syntax is key[,key[,...]].Choose a
179 <rules> is a single argument in the form of a comma-separated list,
180 which offers a way to specify individual culling rules. The recognized
182 <rules> can be specified by the sequence of keys k1,k2, ..., as described in
203 which offers a way to specify individual selecting rules.
|
| /linux/tools/power/acpi/tools/ec/ |
| H A D | Makefile | 14 include ../../Makefile.rules
|
| /linux/Documentation/ABI/testing/ |
| H A D | ima_policy | 11 by opening the file, writing the rules one at a time and
141 Example of measure rules using alternate PCRs::
171 Example of 'measure' and 'appraise' rules requiring fs-verity
188 All of these policy rules could, for example, be constrained
|
| /linux/Documentation/arch/powerpc/ |
| H A D | syscall64-abi.rst | 19 rules, with the following differences.
47 Register preservation rules
49 Register preservation rules match the ELF ABI calling sequence with some
136 Register preservation rules
|
| /linux/Documentation/translations/zh_TW/process/ |
| H A D | license-rules.rst | 5 :Original: :ref:`Documentation/process/license-rules.rst <kernel_licensing>`
188 guidelines in the licensing rules documentation.
203 guidelines in the licensing rules documentation.
243 guidelines in the licensing rules documentation.
|
| H A D | howto.rst | 70 :ref:`Documentation/translations/zh_TW/process/license-rules.rst <tw_kernel_licensing>`
141 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
273 內核源碼中的 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
|
| /linux/arch/um/os-Linux/skas/ |
| H A D | Makefile | 10 include $(srctree)/arch/um/scripts/Makefile.rules
|
| /linux/Documentation/bpf/ |
| H A D | bpf_licensing.rst | 65 under these rules:
66 Documentation/process/license-rules.rst
74 kernel. BPF program loading follows the same license checking rules as kernel
|