Searched full:rules (Results 1 – 25 of 296) sorted by relevance
12345678910>>...12
| /Documentation/admin-guide/aoe/ |
| D | udev.txt | 1 # These rules tell udev what device nodes to create for aoe support.
11 # udev_rules="/etc/udev/rules.d/"
12 # bash# ls /etc/udev/rules.d/
13 # 10-wacom.rules 50-udev.rules
15 # /etc/udev/rules.d/60-aoe.rules
|
| D | udev-install.sh | 1 # install the aoe-specific udev rules from udev.txt into
22 # find the directory where udev rules are stored, often
23 # /etc/udev/rules.d
27 rules_d=/etc/udev/rules.d
30 echo "$me Error: cannot find udev rules directory" 1>&2
33 sh -xc "cp `dirname $0`/udev.txt $rules_d/60-aoe.rules"
|
| D | examples.rst | 1 Example of udev rules
7 Example of udev install rules script
|
| /Documentation/networking/ |
| D | tc-actions-env-rules.rst | 4 TC Actions - Environmental Rules
8 The "environmental" rules for authors of any new tc actions are:
23 The "environmental" rules for callers of actions (qdiscs etc) are:
|
| 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 …]
|
| 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 …]
|
| /Documentation/sound/designs/ |
| D | tracepoints.rst | 116 struct snd_pcm_hardware and rules of constraints in the runtime. The
117 structure describes capabilities of handled hardware. The rules describes
120 to compute the target parameter. ALSA PCM core registers some rules to the
129 2. In the same callback, drivers are also expected to register additional rules
156 device, rules of constraint and name of the changed parameter, in order. The
157 field for rules of constraint consists of two sub-fields; index of applied rule
158 and total number of rules added to the runtime. As an exception, the index 000
159 means that the parameter is changed by ALSA PCM core, regardless of the rules.
|
| /Documentation/networking/devlink/ |
| D | devlink-eswitch-attr.rst | 8 Legacy mode operates based on traditional MAC/VLAN steering rules. Switching
10 to offload switching rules to hardware.
14 rules and logic can be offloaded to the hardware switch ASIC. It enables
39 rules.
|
| /Documentation/ABI/testing/ |
| D | sysfs-block-dm | 7 Users: util-linux, device-mapper udev rules
16 Users: util-linux, device-mapper udev rules
25 Users: util-linux, device-mapper udev rules
|
| 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
|
| /Documentation/admin-guide/LSM/ |
| D | Smack.rst | 50 load the Smack access rules
154 This interface allows modification of existing access control rules.
217 This interface allows access control rules in addition to
218 the system defined rules to be specified. The format accepted
232 This interface allows access control rules in addition to
233 the system defined rules to be specified. The format accepted
248 This interface allows process specific access rules to be
249 defined. These rules are only consulted if access would
255 This interface allows process specific access rules to be
256 defined. These rules are only consulted if access would
[all …]
|
| /Documentation/translations/zh_TW/process/ |
| D | index.rst | 37 license-rules
49 stable-kernel-rules
|
| /Documentation/userspace-api/ |
| 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
132 This enables the creation of an inclusive ruleset that will contain our rules.
[all …]
|
| /Documentation/arch/arm/ |
| 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:
|
| /Documentation/translations/zh_CN/process/ |
| D | index.rst | 27 license-rules
66 stable-kernel-rules
|
| /Documentation/process/ |
| 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
|
| /Documentation/kbuild/ |
| D | gendwarfksyms.rst | 107 kABI rules
110 kABI rules allow distributions to fine-tune certain parts
112 versions are calculated. These rules are defined in the
119 the rules. The fields are as follows:
128 The following helper macros, for example, can be used to specify rules
141 Currently, only the rules discussed in this section are supported, but
142 the format is extensible enough to allow further rules to be added as
275 targeted kABI rules can become tedious. The `type_string` rule allows us argument
318 alignment holes can potentially be used instead. While kABI rules could
|
| /Documentation/infiniband/ |
| D | tag_matching.rst | 5 The MPI standard defines a set of rules, known as tag-matching, for matching
14 The ordering rules require that when more than one pair of send and receive
19 earlier tags can’t be used to satisfy the matching rules.
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 20 1. read access. Locking rules:
24 2. object creation. Locking rules:
28 3. object removal. Locking rules:
34 4. link creation. Locking rules:
40 5. rename that is _not_ cross-directory. Locking rules:
53 6. cross-directory rename. The trickiest in the whole bunch. Locking rules:
65 The rules above obviously guarantee that all directories that are going
121 on other filesystems must follow the same locking rules. Moreover, "a
|
| /Documentation/bpf/ |
| 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
|
| /Documentation/mm/ |
| 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.
|
| /Documentation/driver-api/firmware/ |
| D | firmware-usage-guidelines.rst | 10 Drivers that use firmware from linux-firmware should follow the rules in
13 then of course these rules will not apply strictly.)
|
| /Documentation/userspace-api/gpio/ |
| D | gpio-get-linehandle-ioctl.rst | 55 .. _gpio-get-linehandle-config-rules:
57 Configuration Rules
60 The following configuration rules apply:
|
| /Documentation/arch/powerpc/ |
| 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
55 | Register | Preservation Rules | Purpose |
73 | Register | Preservation Rules | Purpose |
136 Register preservation rules
|
| /Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | kconfig.rst | 20 | ports to Bridge and offloading rules for traffic between such ports.
78 | flow rules to direct traffic into arbitrary rx queue via ethtool set/get_rxnfc API.
139 | Support offloading connection tracking rules via tc ct action.
144 | Support offloading sample rules via tc sample action.
|
12345678910>>...12