| /linux-4.4.14/drivers/s390/net/ |
| D | qeth_core_sys.c | 445 switch (card->options.isolation) { in qeth_dev_isolation_show()
461 enum qeth_ipa_isolation_modes isolation; in qeth_dev_isolation_store() local
480 isolation = ISOLATION_MODE_NONE; in qeth_dev_isolation_store()
482 isolation = ISOLATION_MODE_FWD; in qeth_dev_isolation_store()
484 isolation = ISOLATION_MODE_DROP; in qeth_dev_isolation_store()
492 card->options.prev_isolation = card->options.isolation; in qeth_dev_isolation_store()
493 card->options.isolation = isolation; in qeth_dev_isolation_store()
504 static DEVICE_ATTR(isolation, 0644, qeth_dev_isolation_show,
|
| D | qeth_core_main.c | 1402 card->options.isolation = ISOLATION_MODE_NONE; in qeth_set_intial_options()
4283 if (card->options.isolation == ISOLATION_MODE_NONE) { in qeth_setadpparms_set_access_ctrl_cb()
4295 card->options.isolation = card->options.prev_isolation; in qeth_setadpparms_set_access_ctrl_cb()
4301 card->options.isolation = card->options.prev_isolation; in qeth_setadpparms_set_access_ctrl_cb()
4312 card->options.isolation = card->options.prev_isolation; in qeth_setadpparms_set_access_ctrl_cb()
4318 card->options.isolation = card->options.prev_isolation; in qeth_setadpparms_set_access_ctrl_cb()
4324 card->options.isolation = card->options.prev_isolation; in qeth_setadpparms_set_access_ctrl_cb()
4330 card->options.isolation = card->options.prev_isolation; in qeth_setadpparms_set_access_ctrl_cb()
4339 card->options.isolation = card->options.prev_isolation; in qeth_setadpparms_set_access_ctrl_cb()
4347 enum qeth_ipa_isolation_modes isolation, int fallback) in qeth_setadpparms_set_access_ctrl() argument
[all …]
|
| D | qeth_core.h | 695 enum qeth_ipa_isolation_modes isolation; member
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | devpts.txt | 126 does not provide strict isolation in a container environment. i.e by
130 To workaround this and have strict isolation, all mounts of devpts,
|
| D | xfs-self-describing-metadata.txt | 42 you can't look at a single metadata block in isolation and say "yes, it is
|
| /linux-4.4.14/Documentation/devicetree/bindings/phy/ |
| D | samsung-phy.txt | 24 control pmu registers for power isolation.
152 control pmu registers for power isolation.
|
| /linux-4.4.14/Documentation/block/ |
| D | cfq-iosched.txt | 29 side is that isolation provided from WRITES also goes down and notion of
257 tree idling provides isolation with buffered write queues on async tree.
264 with REQ_NOIDLE. This helps in providing isolation with all the sync-idle
285 provides isolation from multiple sequential readers and at the same
|
| D | data-integrity.txt | 28 allows not only corruption prevention but also isolation of the point
|
| /linux-4.4.14/Documentation/ |
| D | vfio.txt | 44 isolation properties into what was, in many cases, an interface only
50 This isolation is not always at the granularity of a single device
52 interconnects, and IOMMU topologies can each reduce this isolation.
301 out of the window leads to the whole PE isolation.
499 still provide isolation. For PCI, SR-IOV Virtual Functions are the
|
| D | kernel-parameters.txt | 440 force_isolation - Force device isolation for all
442 allowed anymore to lift isolation
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-class-net-mesh | 75 Defines the isolation mark (and its bitmask) which
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | msi.txt | 28 MSI controller and device rather than a property of either in isolation).
|
| /linux-4.4.14/drivers/staging/fsl-mc/ |
| D | README.txt | 124 All objects in a container share the same hardware "isolation context".
125 This means that with respect to an IOMMU the isolation granularity
|
| /linux-4.4.14/Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 22 * Provide address space isolation between multiple contexts.
|
| /linux-4.4.14/drivers/net/wireless/b43/ |
| D | phy_lp.c | 173 u16 isolation; in lpphy_adjust_gain_table() local
178 isolation = lpphy->tx_isolation_med_band; in lpphy_adjust_gain_table()
180 isolation = lpphy->tx_isolation_low_band; in lpphy_adjust_gain_table()
182 isolation = lpphy->tx_isolation_med_band; in lpphy_adjust_gain_table()
184 isolation = lpphy->tx_isolation_hi_band; in lpphy_adjust_gain_table()
186 temp[0] = ((isolation - 26) / 12) << 12; in lpphy_adjust_gain_table()
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | pci_iov_resource_on_powernv.txt | 15 associated with a device or a set of devices to provide isolation between
298 possible, but the isolation isn't as good, and it reduces the number of PE#
|
| /linux-4.4.14/Documentation/misc-devices/mei/ |
| D | mei.txt | 36 - Selective network isolation of Ethernet and IP protocol flows based
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.pvrusb2 | 113 however the design goals (strict isolation) and physical layer
|
| /linux-4.4.14/Documentation/x86/x86_64/ |
| D | boot-options.txt | 273 (PCI bus number 0); if translation (isolation) is enabled on this
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-deadline.txt | 61 interference between different tasks (bandwidth isolation), while the EDF[1]
462 of retaining bandwidth isolation among non-interacting tasks. This is
|
| /linux-4.4.14/init/ |
| D | Kconfig | 933 controls or device isolation.
936 - Documentation/cgroups/ (features for grouping, isolation
|
| /linux-4.4.14/Documentation/security/ |
| D | Smack.txt | 421 With the isolation provided by Smack access separation is simple. There are
|
| /linux-4.4.14/Documentation/networking/ |
| D | ip-sysctl.txt | 1011 Hewlett-Packard call it Source-Port filtering or port-isolation.
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | README.OSS | 371 PnP isolation tool. When writing this there is a pre alpha test version
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig | 814 isolation, where all DMAs pass through the IOMMU. This
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | api.txt | 1340 isolation of the device. Usages not specifying this flag are deprecated.
|