Home
last modified time | relevance | path

Searched full:therefore (Results 1 – 25 of 2177) sorted by relevance

12345678910>>...88

/kernel/linux/linux-5.10/Documentation/networking/
Dx25.rst15 I therefore decided to write the implementation such that as far as the
17 layer of the Linux kernel and therefore it did not concern itself with
18 implementation of LAPB. Therefore the LAPB modules would be called by
Dgtp.rst173 Therefore:
189 Therefore no two remote GTP-U endpoints shall send traffic to a
199 Therefore, the receiving side identifies tunnels exclusively based on
242 Therefore for a given UE the mapping in IP to PDN network is:
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/hamradio/
Dbaycom.rst22 therefore it supports just about every bit bang modem on a
65 and can therefore be fed from the parallel port and does not require
89 but they are now true kernel network interfaces. Installation is therefore
143 a reasonable DCD algorithm in software. Therefore, if your radio
159 startup time. Therefore the baycom drivers subsequently won't be able to
160 access a serial port. You might therefore find it necessary to release
/kernel/linux/linux-5.10/include/crypto/
Dxts.h15 * key consists of keys of equal size concatenated, therefore in xts_check_key()
32 * key consists of keys of equal size concatenated, therefore in xts_verify_key()
/kernel/linux/linux-5.10/arch/x86/include/uapi/asm/
Dldt.h19 * call is more for 32bit mode therefore.
34 * programs can pass uninitialized values here. Therefore, in
/kernel/linux/linux-5.10/Documentation/
Datomic_t.txt67 Therefore, an explicitly unsigned variant of the atomic ops is strictly
84 smp_store_release() respectively. Therefore, if you find yourself only using
143 reversible. Bitops are irreversible and therefore the modified value
184 subsequent. Therefore a fully ordered primitive is like having an smp_mb()
/kernel/linux/linux-5.10/drivers/pci/controller/dwc/
DKconfig117 DesignWare hardware and therefore the driver re-uses the
129 on DesignWare hardware and therefore the driver re-uses the
185 DesignWare hardware and therefore the driver re-uses the
247 and therefore the driver re-uses the DesignWare core functions to
/kernel/linux/linux-5.10/arch/arm64/kvm/
Dinject_fault.c177 * VCPU therefore is not currently executing guest code.
193 * VCPU therefore is not currently executing guest code.
208 * VCPU therefore is not currently executing guest code.
229 * VCPU therefore is not currently executing guest code.
/kernel/linux/linux-5.10/tools/arch/sparc/include/asm/
Dbarrier_64.h10 * Therefore, if interrupts are disabled, the chip can hang forever.
24 * The branch has to be mispredicted for the bug to occur. Therefore, we put
/kernel/linux/linux-5.10/arch/sparc/include/asm/
Dbarrier_64.h8 * Therefore, if interrupts are disabled, the chip can hang forever.
22 * The branch has to be mispredicted for the bug to occur. Therefore, we put
/kernel/linux/linux-5.10/tools/power/cpupower/man/
Dcpupower-monitor.195 left. Therefore there can be some inaccuracy when cores are in an idle
131 The registers are accessed via PCI and therefore can still be read out while
138 Therefore this counter can be used to verify whether the graphics' driver
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/virtio/
Diommu.txt6 masters. Therefore, the PCI root complex that hosts the virtio-iommu
24 - DMA from the IOMMU device isn't managed by another IOMMU. Therefore the
/kernel/linux/linux-5.10/Documentation/RCU/
DUP.rst46 Therefore, in this case, allowing call_rcu() to immediately invoke
109 list, and is therefore within an RCU read-side critical section.
110 Therefore, the called function has been invoked within an RCU
/kernel/linux/linux-5.10/Documentation/driver-api/
Dvfio.rst67 Therefore, while for the most part an IOMMU may have device level
69 IOMMU API therefore supports a notion of IOMMU groups. A group is
71 system. Groups are therefore the unit of ownership used by VFIO.
126 This device is therefore in IOMMU group 26. This device is on the
127 pci bus, therefore the user will make use of vfio-pci to manage the
152 This device is behind a PCIe-to-PCI bridge [4]_, therefore we also
155 not currently have a host driver, therefore it's not required to
161 no capabilities on its own and is therefore expected to be set to
/kernel/linux/linux-5.10/Documentation/crypto/
Dintro.rst19 Therefore, a cipher handle variable usually has the name "tfm". Besides
68 returned to the consumer. Therefore, please refer to all initialization
/kernel/linux/linux-5.10/include/linux/mtd/
Dxip.h27 * obviously not be running from flash. The __xipram is therefore marking
70 #warning "your system will therefore be unresponsive when writing or erasing flash"
/kernel/linux/linux-5.10/drivers/scsi/pcmcia/
Dnsp_message.c21 * therefore we should poll the scsi phase here to catch in nsp_message_in()
62 * therefore we should poll the scsi phase here to catch in nsp_message_out()
/kernel/linux/linux-5.10/Documentation/filesystems/ext4/
Dallocators.rst14 up file rewrites significantly. Therefore, it is useful to reduce
40 here is that all the files in a directory might be related, therefore it
/kernel/linux/linux-5.10/arch/arm64/kernel/vdso/
Dsigreturn.S28 * the sigcontext. Re-enabling the cfi directives here therefore needs to be
66 * instruction sequence to unwind from signal handlers. We cannot, therefore,
/kernel/linux/linux-5.10/Documentation/RCU/Design/Requirements/
DRequirements.rst27 This document therefore summarizes RCU's requirements, and can be
110 started after the ``synchronize_rcu()`` started, and must therefore also
111 load a value of one from ``x``. Therefore, the outcome:
249 optimizations could cause trouble. Therefore, we clearly need some way
569 | Therefore, there absolutely must be a full memory barrier between the |
645 guarantee. Therefore, the justification for adding a conditional
682 therefore all too easy to assume that RCU is guaranteeing more than it
804 | ``synchronize_rcu()`` completed. Therefore, the code following |
987 | Therefore, even in practice, RCU users must abide by the theoretical |
995 RCU implementation must abide by them. They therefore bear repeating:
[all …]
/kernel/linux/linux-5.10/arch/sparc/kernel/
Dktlb.S24 /* The kernel executes in context zero, therefore we do not
136 /* The kernel executes in context zero, therefore we do not
263 /* The kernel executes in context zero, therefore we do not
/kernel/linux/linux-5.10/Documentation/core-api/
Dpacking.rst40 over CPU endianness and therefore between possible mismatches between
89 Therefore, QUIRK_LITTLE_ENDIAN means that inside the memory region, every
164 durring runtime, therefore it is reasonable for xxx_packing() to return void
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dtegra30-colibri.dtsi163 /* Multiplexed RDnWR and therefore disabled */
171 /* Multiplexed GMI_CLK and therefore disabled */
365 /* Multiplexed and therefore disabled */
408 * pins multiplexed with others and therefore disabled
467 /* Multiplexed SSPFRM, SSPTXD and therefore disabled */
538 /* Colibri VGA not supported and therefore disabled */
602 /* Not connected and therefore disabled */
680 * temperature sensor therefore requires disabling for
/kernel/linux/linux-5.10/include/linux/
Dcnt32_to_63.h34 * Many hardware clock counters are only 32 bits wide and therefore have
88 * implicitly by making the multiplier even, therefore saving on a runtime
/kernel/linux/linux-5.10/Documentation/scsi/
Daha152x.rst134 Therefore the SCSI BIOS/DOS driver has to calculate a logical/virtual
142 in the partition table and therefore every operating system has to know
155 address the first GB of your disk in the partition table. Therefore

12345678910>>...88