Loading CREDITS +24 −0 Original line number Original line Diff line number Diff line Loading @@ -710,6 +710,10 @@ S: Las Cuevas 2385 - Bo Guemes S: Las Heras, Mendoza CP 5539 S: Las Heras, Mendoza CP 5539 S: Argentina S: Argentina N: Jay Cliburn E: jcliburn@gmail.com D: ATLX Ethernet drivers N: Steven P. Cole N: Steven P. Cole E: scole@lanl.gov E: scole@lanl.gov E: elenstev@mesatop.com E: elenstev@mesatop.com Loading Loading @@ -1284,6 +1288,10 @@ D: Major kbuild rework during the 2.5 cycle D: ISDN Maintainer D: ISDN Maintainer S: USA S: USA N: Gerrit Renker E: gerrit@erg.abdn.ac.uk D: DCCP protocol support. N: Philip Gladstone N: Philip Gladstone E: philip@gladstonefamily.net E: philip@gladstonefamily.net D: Kernel / timekeeping stuff D: Kernel / timekeeping stuff Loading Loading @@ -2138,6 +2146,10 @@ E: seasons@falcon.sch.bme.hu E: seasons@makosteszta.sote.hu E: seasons@makosteszta.sote.hu D: Original author of software suspend D: Original author of software suspend N: Alexey Kuznetsov E: kuznet@ms2.inr.ac.ru D: Author and maintainer of large parts of the networking stack N: Jaroslav Kysela N: Jaroslav Kysela E: perex@perex.cz E: perex@perex.cz W: https://www.perex.cz W: https://www.perex.cz Loading Loading @@ -2696,6 +2708,10 @@ N: Wolfgang Muees E: wolfgang@iksw-muees.de E: wolfgang@iksw-muees.de D: Auerswald USB driver D: Auerswald USB driver N: Shrijeet Mukherjee E: shrijeet@gmail.com D: Network routing domains (VRF). N: Paul Mundt N: Paul Mundt E: paul.mundt@gmail.com E: paul.mundt@gmail.com D: SuperH maintainer D: SuperH maintainer Loading Loading @@ -4110,6 +4126,10 @@ S: B-1206 Jingmao Guojigongyu S: 16 Baliqiao Nanjie, Beijing 101100 S: 16 Baliqiao Nanjie, Beijing 101100 S: People's Repulic of China S: People's Repulic of China N: Aviad Yehezkel E: aviadye@nvidia.com D: Kernel TLS implementation and offload support. N: Victor Yodaiken N: Victor Yodaiken E: yodaiken@fsmlabs.com E: yodaiken@fsmlabs.com D: RTLinux (RealTime Linux) D: RTLinux (RealTime Linux) Loading Loading @@ -4167,6 +4187,10 @@ S: 1507 145th Place SE #B5 S: Bellevue, Washington 98007 S: Bellevue, Washington 98007 S: USA S: USA N: Wensong Zhang E: wensong@linux-vs.org D: IP virtual server (IPVS). N: Haojian Zhuang N: Haojian Zhuang E: haojian.zhuang@gmail.com E: haojian.zhuang@gmail.com D: MMP support D: MMP support Loading Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.rst +4 −4 Original line number Original line Diff line number Diff line Loading @@ -473,7 +473,7 @@ read-side critical sections that follow the idle period (the oval near the bottom of the diagram above). the bottom of the diagram above). Plumbing this into the full grace-period execution is described Plumbing this into the full grace-period execution is described `below <#Forcing%20Quiescent%20States>`__. `below <Forcing Quiescent States_>`__. CPU-Hotplug Interface CPU-Hotplug Interface ^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^ Loading @@ -494,7 +494,7 @@ mask to detect CPUs having gone offline since the beginning of this grace period. grace period. Plumbing this into the full grace-period execution is described Plumbing this into the full grace-period execution is described `below <#Forcing%20Quiescent%20States>`__. `below <Forcing Quiescent States_>`__. Forcing Quiescent States Forcing Quiescent States ^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ Loading Loading @@ -532,7 +532,7 @@ from other CPUs. | RCU. But this diagram is complex enough as it is, so simplicity | | RCU. But this diagram is complex enough as it is, so simplicity | | overrode accuracy. You can think of it as poetic license, or you can | | overrode accuracy. You can think of it as poetic license, or you can | | think of it as misdirection that is resolved in the | | think of it as misdirection that is resolved in the | | `stitched-together diagram <#Putting%20It%20All%20Together>`__. | | `stitched-together diagram <Putting It All Together_>`__. | +-----------------------------------------------------------------------+ +-----------------------------------------------------------------------+ Grace-Period Cleanup Grace-Period Cleanup Loading Loading @@ -596,7 +596,7 @@ maintain ordering. For example, if the callback function wakes up a task that runs on some other CPU, proper ordering must in place in both the that runs on some other CPU, proper ordering must in place in both the callback function and the task being awakened. To see why this is callback function and the task being awakened. To see why this is important, consider the top half of the `grace-period important, consider the top half of the `grace-period cleanup <#Grace-Period%20Cleanup>`__ diagram. The callback might be cleanup`_ diagram. The callback might be running on a CPU corresponding to the leftmost leaf ``rcu_node`` running on a CPU corresponding to the leftmost leaf ``rcu_node`` structure, and awaken a task that is to run on a CPU corresponding to structure, and awaken a task that is to run on a CPU corresponding to the rightmost leaf ``rcu_node`` structure, and the grace-period kernel the rightmost leaf ``rcu_node`` structure, and the grace-period kernel Loading Documentation/RCU/Design/Requirements/Requirements.rst +10 −10 Original line number Original line Diff line number Diff line Loading @@ -45,7 +45,7 @@ requirements: #. `Other RCU Flavors`_ #. `Other RCU Flavors`_ #. `Possible Future Changes`_ #. `Possible Future Changes`_ This is followed by a `summary <#Summary>`__, however, the answers to This is followed by a summary_, however, the answers to each quick quiz immediately follows the quiz. Select the big white space each quick quiz immediately follows the quiz. Select the big white space with your mouse to see the answer. with your mouse to see the answer. Loading Loading @@ -1096,7 +1096,7 @@ memory barriers. | case, voluntary context switch) within an RCU read-side critical | | case, voluntary context switch) within an RCU read-side critical | | section. However, sleeping locks may be used within userspace RCU | | section. However, sleeping locks may be used within userspace RCU | | read-side critical sections, and also within Linux-kernel sleepable | | read-side critical sections, and also within Linux-kernel sleepable | | RCU `(SRCU) <#Sleepable%20RCU>`__ read-side critical sections. In | | RCU `(SRCU) <Sleepable RCU_>`__ read-side critical sections. In | | addition, the -rt patchset turns spinlocks into a sleeping locks so | | addition, the -rt patchset turns spinlocks into a sleeping locks so | | that the corresponding critical sections can be preempted, which also | | that the corresponding critical sections can be preempted, which also | | means that these sleeplockified spinlocks (but not other sleeping | | means that these sleeplockified spinlocks (but not other sleeping | Loading Loading @@ -1186,7 +1186,7 @@ non-preemptible (``CONFIG_PREEMPT=n``) kernels, and thus `tiny RCU <https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com>`__ RCU <https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com>`__ was born. Josh Triplett has since taken over the small-memory banner was born. Josh Triplett has since taken over the small-memory banner with his `Linux kernel tinification <https://tiny.wiki.kernel.org/>`__ with his `Linux kernel tinification <https://tiny.wiki.kernel.org/>`__ project, which resulted in `SRCU <#Sleepable%20RCU>`__ becoming optional project, which resulted in `SRCU <Sleepable RCU_>`__ becoming optional for those kernels not needing it. for those kernels not needing it. The remaining performance requirements are, for the most part, The remaining performance requirements are, for the most part, Loading Loading @@ -1457,8 +1457,8 @@ will vary as the value of ``HZ`` varies, and can also be changed using the relevant Kconfig options and kernel boot parameters. RCU currently the relevant Kconfig options and kernel boot parameters. RCU currently does not do much sanity checking of these parameters, so please use does not do much sanity checking of these parameters, so please use caution when changing them. Note that these forward-progress measures caution when changing them. Note that these forward-progress measures are provided only for RCU, not for `SRCU <#Sleepable%20RCU>`__ or `Tasks are provided only for RCU, not for `SRCU <Sleepable RCU_>`__ or `Tasks RCU <#Tasks%20RCU>`__. RCU`_. RCU takes the following steps in ``call_rcu()`` to encourage timely RCU takes the following steps in ``call_rcu()`` to encourage timely invocation of callbacks when any given non-\ ``rcu_nocbs`` CPU has invocation of callbacks when any given non-\ ``rcu_nocbs`` CPU has Loading @@ -1477,8 +1477,8 @@ encouragement was provided: Again, these are default values when running at ``HZ=1000``, and can be Again, these are default values when running at ``HZ=1000``, and can be overridden. Again, these forward-progress measures are provided only for overridden. Again, these forward-progress measures are provided only for RCU, not for `SRCU <#Sleepable%20RCU>`__ or `Tasks RCU, not for `SRCU <Sleepable RCU_>`__ or `Tasks RCU <#Tasks%20RCU>`__. Even for RCU, callback-invocation forward RCU`_. Even for RCU, callback-invocation forward progress for ``rcu_nocbs`` CPUs is much less well-developed, in part progress for ``rcu_nocbs`` CPUs is much less well-developed, in part because workloads benefiting from ``rcu_nocbs`` CPUs tend to invoke because workloads benefiting from ``rcu_nocbs`` CPUs tend to invoke ``call_rcu()`` relatively infrequently. If workloads emerge that need ``call_rcu()`` relatively infrequently. If workloads emerge that need Loading Loading @@ -1920,7 +1920,7 @@ Hotplug CPU The Linux kernel supports CPU hotplug, which means that CPUs can come The Linux kernel supports CPU hotplug, which means that CPUs can come and go. It is of course illegal to use any RCU API member from an and go. It is of course illegal to use any RCU API member from an offline CPU, with the exception of `SRCU <#Sleepable%20RCU>`__ read-side offline CPU, with the exception of `SRCU <Sleepable RCU_>`__ read-side critical sections. This requirement was present from day one in critical sections. This requirement was present from day one in DYNIX/ptx, but on the other hand, the Linux kernel's CPU-hotplug DYNIX/ptx, but on the other hand, the Linux kernel's CPU-hotplug implementation is “interesting.” implementation is “interesting.” Loading Loading @@ -2177,7 +2177,7 @@ handles these states differently: However, RCU must be reliably informed as to whether any given CPU is However, RCU must be reliably informed as to whether any given CPU is currently in the idle loop, and, for ``NO_HZ_FULL``, also whether that currently in the idle loop, and, for ``NO_HZ_FULL``, also whether that CPU is executing in usermode, as discussed CPU is executing in usermode, as discussed `earlier <#Energy%20Efficiency>`__. It also requires that the `earlier <Energy Efficiency_>`__. It also requires that the scheduling-clock interrupt be enabled when RCU needs it to be: scheduling-clock interrupt be enabled when RCU needs it to be: #. If a CPU is either idle or executing in usermode, and RCU believes it #. If a CPU is either idle or executing in usermode, and RCU believes it Loading Loading @@ -2294,7 +2294,7 @@ Performance, Scalability, Response Time, and Reliability ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Expanding on the `earlier Expanding on the `earlier discussion <#Performance%20and%20Scalability>`__, RCU is used heavily by discussion <Performance and Scalability_>`__, RCU is used heavily by hot code paths in performance-critical portions of the Linux kernel's hot code paths in performance-critical portions of the Linux kernel's networking, security, virtualization, and scheduling code paths. RCU networking, security, virtualization, and scheduling code paths. RCU must therefore use efficient implementations, especially in its must therefore use efficient implementations, especially in its Loading Documentation/admin-guide/binfmt-misc.rst +2 −2 Original line number Original line Diff line number Diff line Loading @@ -23,7 +23,7 @@ Here is what the fields mean: - ``name`` - ``name`` is an identifier string. A new /proc file will be created with this is an identifier string. A new /proc file will be created with this ``name below /proc/sys/fs/binfmt_misc``; cannot contain slashes ``/`` for name below ``/proc/sys/fs/binfmt_misc``; cannot contain slashes ``/`` for obvious reasons. obvious reasons. - ``type`` - ``type`` is the type of recognition. Give ``M`` for magic and ``E`` for extension. is the type of recognition. Give ``M`` for magic and ``E`` for extension. Loading Loading @@ -83,7 +83,7 @@ Here is what the fields mean: ``F`` - fix binary ``F`` - fix binary The usual behaviour of binfmt_misc is to spawn the The usual behaviour of binfmt_misc is to spawn the binary lazily when the misc format file is invoked. However, binary lazily when the misc format file is invoked. However, this doesn``t work very well in the face of mount namespaces and this doesn't work very well in the face of mount namespaces and changeroots, so the ``F`` mode opens the binary as soon as the changeroots, so the ``F`` mode opens the binary as soon as the emulation is installed and uses the opened image to spawn the emulation is installed and uses the opened image to spawn the emulator, meaning it is always available once installed, emulator, meaning it is always available once installed, Loading Documentation/admin-guide/bootconfig.rst +1 −1 Original line number Original line Diff line number Diff line Loading @@ -154,7 +154,7 @@ get the boot configuration data. Because of this "piggyback" method, there is no need to change or Because of this "piggyback" method, there is no need to change or update the boot loader and the kernel image itself as long as the boot update the boot loader and the kernel image itself as long as the boot loader passes the correct initrd file size. If by any chance, the boot loader passes the correct initrd file size. If by any chance, the boot loader passes a longer size, the kernel feils to find the bootconfig data. loader passes a longer size, the kernel fails to find the bootconfig data. To do this operation, Linux kernel provides "bootconfig" command under To do this operation, Linux kernel provides "bootconfig" command under tools/bootconfig, which allows admin to apply or delete the config file tools/bootconfig, which allows admin to apply or delete the config file Loading Loading
CREDITS +24 −0 Original line number Original line Diff line number Diff line Loading @@ -710,6 +710,10 @@ S: Las Cuevas 2385 - Bo Guemes S: Las Heras, Mendoza CP 5539 S: Las Heras, Mendoza CP 5539 S: Argentina S: Argentina N: Jay Cliburn E: jcliburn@gmail.com D: ATLX Ethernet drivers N: Steven P. Cole N: Steven P. Cole E: scole@lanl.gov E: scole@lanl.gov E: elenstev@mesatop.com E: elenstev@mesatop.com Loading Loading @@ -1284,6 +1288,10 @@ D: Major kbuild rework during the 2.5 cycle D: ISDN Maintainer D: ISDN Maintainer S: USA S: USA N: Gerrit Renker E: gerrit@erg.abdn.ac.uk D: DCCP protocol support. N: Philip Gladstone N: Philip Gladstone E: philip@gladstonefamily.net E: philip@gladstonefamily.net D: Kernel / timekeeping stuff D: Kernel / timekeeping stuff Loading Loading @@ -2138,6 +2146,10 @@ E: seasons@falcon.sch.bme.hu E: seasons@makosteszta.sote.hu E: seasons@makosteszta.sote.hu D: Original author of software suspend D: Original author of software suspend N: Alexey Kuznetsov E: kuznet@ms2.inr.ac.ru D: Author and maintainer of large parts of the networking stack N: Jaroslav Kysela N: Jaroslav Kysela E: perex@perex.cz E: perex@perex.cz W: https://www.perex.cz W: https://www.perex.cz Loading Loading @@ -2696,6 +2708,10 @@ N: Wolfgang Muees E: wolfgang@iksw-muees.de E: wolfgang@iksw-muees.de D: Auerswald USB driver D: Auerswald USB driver N: Shrijeet Mukherjee E: shrijeet@gmail.com D: Network routing domains (VRF). N: Paul Mundt N: Paul Mundt E: paul.mundt@gmail.com E: paul.mundt@gmail.com D: SuperH maintainer D: SuperH maintainer Loading Loading @@ -4110,6 +4126,10 @@ S: B-1206 Jingmao Guojigongyu S: 16 Baliqiao Nanjie, Beijing 101100 S: 16 Baliqiao Nanjie, Beijing 101100 S: People's Repulic of China S: People's Repulic of China N: Aviad Yehezkel E: aviadye@nvidia.com D: Kernel TLS implementation and offload support. N: Victor Yodaiken N: Victor Yodaiken E: yodaiken@fsmlabs.com E: yodaiken@fsmlabs.com D: RTLinux (RealTime Linux) D: RTLinux (RealTime Linux) Loading Loading @@ -4167,6 +4187,10 @@ S: 1507 145th Place SE #B5 S: Bellevue, Washington 98007 S: Bellevue, Washington 98007 S: USA S: USA N: Wensong Zhang E: wensong@linux-vs.org D: IP virtual server (IPVS). N: Haojian Zhuang N: Haojian Zhuang E: haojian.zhuang@gmail.com E: haojian.zhuang@gmail.com D: MMP support D: MMP support Loading
Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.rst +4 −4 Original line number Original line Diff line number Diff line Loading @@ -473,7 +473,7 @@ read-side critical sections that follow the idle period (the oval near the bottom of the diagram above). the bottom of the diagram above). Plumbing this into the full grace-period execution is described Plumbing this into the full grace-period execution is described `below <#Forcing%20Quiescent%20States>`__. `below <Forcing Quiescent States_>`__. CPU-Hotplug Interface CPU-Hotplug Interface ^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^ Loading @@ -494,7 +494,7 @@ mask to detect CPUs having gone offline since the beginning of this grace period. grace period. Plumbing this into the full grace-period execution is described Plumbing this into the full grace-period execution is described `below <#Forcing%20Quiescent%20States>`__. `below <Forcing Quiescent States_>`__. Forcing Quiescent States Forcing Quiescent States ^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ Loading Loading @@ -532,7 +532,7 @@ from other CPUs. | RCU. But this diagram is complex enough as it is, so simplicity | | RCU. But this diagram is complex enough as it is, so simplicity | | overrode accuracy. You can think of it as poetic license, or you can | | overrode accuracy. You can think of it as poetic license, or you can | | think of it as misdirection that is resolved in the | | think of it as misdirection that is resolved in the | | `stitched-together diagram <#Putting%20It%20All%20Together>`__. | | `stitched-together diagram <Putting It All Together_>`__. | +-----------------------------------------------------------------------+ +-----------------------------------------------------------------------+ Grace-Period Cleanup Grace-Period Cleanup Loading Loading @@ -596,7 +596,7 @@ maintain ordering. For example, if the callback function wakes up a task that runs on some other CPU, proper ordering must in place in both the that runs on some other CPU, proper ordering must in place in both the callback function and the task being awakened. To see why this is callback function and the task being awakened. To see why this is important, consider the top half of the `grace-period important, consider the top half of the `grace-period cleanup <#Grace-Period%20Cleanup>`__ diagram. The callback might be cleanup`_ diagram. The callback might be running on a CPU corresponding to the leftmost leaf ``rcu_node`` running on a CPU corresponding to the leftmost leaf ``rcu_node`` structure, and awaken a task that is to run on a CPU corresponding to structure, and awaken a task that is to run on a CPU corresponding to the rightmost leaf ``rcu_node`` structure, and the grace-period kernel the rightmost leaf ``rcu_node`` structure, and the grace-period kernel Loading
Documentation/RCU/Design/Requirements/Requirements.rst +10 −10 Original line number Original line Diff line number Diff line Loading @@ -45,7 +45,7 @@ requirements: #. `Other RCU Flavors`_ #. `Other RCU Flavors`_ #. `Possible Future Changes`_ #. `Possible Future Changes`_ This is followed by a `summary <#Summary>`__, however, the answers to This is followed by a summary_, however, the answers to each quick quiz immediately follows the quiz. Select the big white space each quick quiz immediately follows the quiz. Select the big white space with your mouse to see the answer. with your mouse to see the answer. Loading Loading @@ -1096,7 +1096,7 @@ memory barriers. | case, voluntary context switch) within an RCU read-side critical | | case, voluntary context switch) within an RCU read-side critical | | section. However, sleeping locks may be used within userspace RCU | | section. However, sleeping locks may be used within userspace RCU | | read-side critical sections, and also within Linux-kernel sleepable | | read-side critical sections, and also within Linux-kernel sleepable | | RCU `(SRCU) <#Sleepable%20RCU>`__ read-side critical sections. In | | RCU `(SRCU) <Sleepable RCU_>`__ read-side critical sections. In | | addition, the -rt patchset turns spinlocks into a sleeping locks so | | addition, the -rt patchset turns spinlocks into a sleeping locks so | | that the corresponding critical sections can be preempted, which also | | that the corresponding critical sections can be preempted, which also | | means that these sleeplockified spinlocks (but not other sleeping | | means that these sleeplockified spinlocks (but not other sleeping | Loading Loading @@ -1186,7 +1186,7 @@ non-preemptible (``CONFIG_PREEMPT=n``) kernels, and thus `tiny RCU <https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com>`__ RCU <https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com>`__ was born. Josh Triplett has since taken over the small-memory banner was born. Josh Triplett has since taken over the small-memory banner with his `Linux kernel tinification <https://tiny.wiki.kernel.org/>`__ with his `Linux kernel tinification <https://tiny.wiki.kernel.org/>`__ project, which resulted in `SRCU <#Sleepable%20RCU>`__ becoming optional project, which resulted in `SRCU <Sleepable RCU_>`__ becoming optional for those kernels not needing it. for those kernels not needing it. The remaining performance requirements are, for the most part, The remaining performance requirements are, for the most part, Loading Loading @@ -1457,8 +1457,8 @@ will vary as the value of ``HZ`` varies, and can also be changed using the relevant Kconfig options and kernel boot parameters. RCU currently the relevant Kconfig options and kernel boot parameters. RCU currently does not do much sanity checking of these parameters, so please use does not do much sanity checking of these parameters, so please use caution when changing them. Note that these forward-progress measures caution when changing them. Note that these forward-progress measures are provided only for RCU, not for `SRCU <#Sleepable%20RCU>`__ or `Tasks are provided only for RCU, not for `SRCU <Sleepable RCU_>`__ or `Tasks RCU <#Tasks%20RCU>`__. RCU`_. RCU takes the following steps in ``call_rcu()`` to encourage timely RCU takes the following steps in ``call_rcu()`` to encourage timely invocation of callbacks when any given non-\ ``rcu_nocbs`` CPU has invocation of callbacks when any given non-\ ``rcu_nocbs`` CPU has Loading @@ -1477,8 +1477,8 @@ encouragement was provided: Again, these are default values when running at ``HZ=1000``, and can be Again, these are default values when running at ``HZ=1000``, and can be overridden. Again, these forward-progress measures are provided only for overridden. Again, these forward-progress measures are provided only for RCU, not for `SRCU <#Sleepable%20RCU>`__ or `Tasks RCU, not for `SRCU <Sleepable RCU_>`__ or `Tasks RCU <#Tasks%20RCU>`__. Even for RCU, callback-invocation forward RCU`_. Even for RCU, callback-invocation forward progress for ``rcu_nocbs`` CPUs is much less well-developed, in part progress for ``rcu_nocbs`` CPUs is much less well-developed, in part because workloads benefiting from ``rcu_nocbs`` CPUs tend to invoke because workloads benefiting from ``rcu_nocbs`` CPUs tend to invoke ``call_rcu()`` relatively infrequently. If workloads emerge that need ``call_rcu()`` relatively infrequently. If workloads emerge that need Loading Loading @@ -1920,7 +1920,7 @@ Hotplug CPU The Linux kernel supports CPU hotplug, which means that CPUs can come The Linux kernel supports CPU hotplug, which means that CPUs can come and go. It is of course illegal to use any RCU API member from an and go. It is of course illegal to use any RCU API member from an offline CPU, with the exception of `SRCU <#Sleepable%20RCU>`__ read-side offline CPU, with the exception of `SRCU <Sleepable RCU_>`__ read-side critical sections. This requirement was present from day one in critical sections. This requirement was present from day one in DYNIX/ptx, but on the other hand, the Linux kernel's CPU-hotplug DYNIX/ptx, but on the other hand, the Linux kernel's CPU-hotplug implementation is “interesting.” implementation is “interesting.” Loading Loading @@ -2177,7 +2177,7 @@ handles these states differently: However, RCU must be reliably informed as to whether any given CPU is However, RCU must be reliably informed as to whether any given CPU is currently in the idle loop, and, for ``NO_HZ_FULL``, also whether that currently in the idle loop, and, for ``NO_HZ_FULL``, also whether that CPU is executing in usermode, as discussed CPU is executing in usermode, as discussed `earlier <#Energy%20Efficiency>`__. It also requires that the `earlier <Energy Efficiency_>`__. It also requires that the scheduling-clock interrupt be enabled when RCU needs it to be: scheduling-clock interrupt be enabled when RCU needs it to be: #. If a CPU is either idle or executing in usermode, and RCU believes it #. If a CPU is either idle or executing in usermode, and RCU believes it Loading Loading @@ -2294,7 +2294,7 @@ Performance, Scalability, Response Time, and Reliability ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Expanding on the `earlier Expanding on the `earlier discussion <#Performance%20and%20Scalability>`__, RCU is used heavily by discussion <Performance and Scalability_>`__, RCU is used heavily by hot code paths in performance-critical portions of the Linux kernel's hot code paths in performance-critical portions of the Linux kernel's networking, security, virtualization, and scheduling code paths. RCU networking, security, virtualization, and scheduling code paths. RCU must therefore use efficient implementations, especially in its must therefore use efficient implementations, especially in its Loading
Documentation/admin-guide/binfmt-misc.rst +2 −2 Original line number Original line Diff line number Diff line Loading @@ -23,7 +23,7 @@ Here is what the fields mean: - ``name`` - ``name`` is an identifier string. A new /proc file will be created with this is an identifier string. A new /proc file will be created with this ``name below /proc/sys/fs/binfmt_misc``; cannot contain slashes ``/`` for name below ``/proc/sys/fs/binfmt_misc``; cannot contain slashes ``/`` for obvious reasons. obvious reasons. - ``type`` - ``type`` is the type of recognition. Give ``M`` for magic and ``E`` for extension. is the type of recognition. Give ``M`` for magic and ``E`` for extension. Loading Loading @@ -83,7 +83,7 @@ Here is what the fields mean: ``F`` - fix binary ``F`` - fix binary The usual behaviour of binfmt_misc is to spawn the The usual behaviour of binfmt_misc is to spawn the binary lazily when the misc format file is invoked. However, binary lazily when the misc format file is invoked. However, this doesn``t work very well in the face of mount namespaces and this doesn't work very well in the face of mount namespaces and changeroots, so the ``F`` mode opens the binary as soon as the changeroots, so the ``F`` mode opens the binary as soon as the emulation is installed and uses the opened image to spawn the emulation is installed and uses the opened image to spawn the emulator, meaning it is always available once installed, emulator, meaning it is always available once installed, Loading
Documentation/admin-guide/bootconfig.rst +1 −1 Original line number Original line Diff line number Diff line Loading @@ -154,7 +154,7 @@ get the boot configuration data. Because of this "piggyback" method, there is no need to change or Because of this "piggyback" method, there is no need to change or update the boot loader and the kernel image itself as long as the boot update the boot loader and the kernel image itself as long as the boot loader passes the correct initrd file size. If by any chance, the boot loader passes the correct initrd file size. If by any chance, the boot loader passes a longer size, the kernel feils to find the bootconfig data. loader passes a longer size, the kernel fails to find the bootconfig data. To do this operation, Linux kernel provides "bootconfig" command under To do this operation, Linux kernel provides "bootconfig" command under tools/bootconfig, which allows admin to apply or delete the config file tools/bootconfig, which allows admin to apply or delete the config file Loading