home.social

Search

320 results for “kernellogger”

  1. Another small step to get #RT aka #Realtime aka #PREEMPT_RT support mainlined was taken, as more preparations for introducing #printk kthreads were merged for #Linux #kernel 6.7: git.kernel.org/torvalds/c/2a80

    That work comes from this series:
    lore.kernel.org/all/2023091619

    But some more work is needed to finally make the #LinuxKernel printk stack be rt capable, as threaded printing, atomic printing regions, or nbcon drivers are still missing afaics.

  2. Another small step to get #RT aka #Realtime aka #PREEMPT_RT support mainlined was taken, as more preparations for introducing #printk kthreads were merged for #Linux #kernel 6.7: git.kernel.org/torvalds/c/2a80

    That work comes from this series:
    lore.kernel.org/all/2023091619

    But some more work is needed to finally make the #LinuxKernel printk stack be rt capable, as threaded printing, atomic printing regions, or nbcon drivers are still missing afaics.

  3. Another small step to get #RT aka #Realtime aka #PREEMPT_RT support mainlined was taken, as more preparations for introducing #printk kthreads were merged for #Linux #kernel 6.7: git.kernel.org/torvalds/c/2a80

    That work comes from this series:
    lore.kernel.org/all/2023091619

    But some more work is needed to finally make the #LinuxKernel printk stack be rt capable, as threaded printing, atomic printing regions, or nbcon drivers are still missing afaics.

  4. Merged for #LinuxKernel 6.2: #printk patches to reduce the console_lock scope.

    They prepare printk for threaded/atomic
    printing, which is needed to finally make printk #PREEMPT_RT (aka #REALTIME) safe: git.kernel.org/torvalds/c/98d0

    More details in the cover letter of the submission of those patches: lore.kernel.org/lkml/202211161 #Linux #kernel

  5. Merged for #LinuxKernel 6.2: #printk patches to reduce the console_lock scope.

    They prepare printk for threaded/atomic
    printing, which is needed to finally make printk #PREEMPT_RT (aka #REALTIME) safe: git.kernel.org/torvalds/c/98d0

    More details in the cover letter of the submission of those patches: lore.kernel.org/lkml/202211161 #Linux #kernel

  6. Merged for #LinuxKernel 6.2: #printk patches to reduce the console_lock scope.

    They prepare printk for threaded/atomic
    printing, which is needed to finally make printk #PREEMPT_RT (aka #REALTIME) safe: git.kernel.org/torvalds/c/98d0

    More details in the cover letter of the submission of those patches: lore.kernel.org/lkml/202211161 #Linux #kernel

  7. Merged for #LinuxKernel 6.2: #printk patches to reduce the console_lock scope.

    They prepare printk for threaded/atomic
    printing, which is needed to finally make printk #PREEMPT_RT (aka #REALTIME) safe: git.kernel.org/torvalds/c/98d0

    More details in the cover letter of the submission of those patches: lore.kernel.org/lkml/202211161 #Linux #kernel

  8. Some highlights from the main #erofs merge for #Linux 7.0:

    git.kernel.org/torvalds/c/3893

    ""
    Inode page cache sharing among filesystems on the same machine is now supported, which is particularly useful for high-density hosts running tens of thousands of containers. [for more about this, see lwn.net/Articles/1055062/]

    In addition, we fully isolate the EROFS core on-disk format from other optional encoded layouts since the core on-disk part is designed to be simple, effective, and secure. Users can use the core format to build unique golden immutable images and import their filesystem […]
    ""

    #Kernel #LinuxKernel

  9. Some highlights from the main #erofs merge for #Linux 7.0:

    git.kernel.org/torvalds/c/3893

    ""
    Inode page cache sharing among filesystems on the same machine is now supported, which is particularly useful for high-density hosts running tens of thousands of containers. [for more about this, see lwn.net/Articles/1055062/]

    In addition, we fully isolate the EROFS core on-disk format from other optional encoded layouts since the core on-disk part is designed to be simple, effective, and secure. Users can use the core format to build unique golden immutable images and import their filesystem […]
    ""

    #Kernel #LinuxKernel

  10. Some highlights from the main merge for 7.0:

    git.kernel.org/torvalds/c/3893

    ""
    Inode page cache sharing among filesystems on the same machine is now supported, which is particularly useful for high-density hosts running tens of thousands of containers. [for more about this, see lwn.net/Articles/1055062/]

    In addition, we fully isolate the EROFS core on-disk format from other optional encoded layouts since the core on-disk part is designed to be simple, effective, and secure. Users can use the core format to build unique golden immutable images and import their filesystem […]
    ""

  11. Some highlights from the main #erofs merge for #Linux 7.0:

    git.kernel.org/torvalds/c/3893

    ""
    Inode page cache sharing among filesystems on the same machine is now supported, which is particularly useful for high-density hosts running tens of thousands of containers. [for more about this, see lwn.net/Articles/1055062/]

    In addition, we fully isolate the EROFS core on-disk format from other optional encoded layouts since the core on-disk part is designed to be simple, effective, and secure. Users can use the core format to build unique golden immutable images and import their filesystem […]
    ""

    #Kernel #LinuxKernel

  12. Some highlights from the main #erofs merge for #Linux 7.0:

    git.kernel.org/torvalds/c/3893

    ""
    Inode page cache sharing among filesystems on the same machine is now supported, which is particularly useful for high-density hosts running tens of thousands of containers. [for more about this, see lwn.net/Articles/1055062/]

    In addition, we fully isolate the EROFS core on-disk format from other optional encoded layouts since the core on-disk part is designed to be simple, effective, and secure. Users can use the core format to build unique golden immutable images and import their filesystem […]
    ""

    #Kernel #LinuxKernel

  13. Highlights from the main #erofs (used by #composefs) merge for #Linux 6.17[1]:

    ""We now support metadata compression. It can be useful for embedded use cases or archiving a large number of small files.

    Additionally, readdir performance has been improved by enabling readahead (note that it was already common practice for ext3/4 non-dx and f2fs directories). We may consider further improvements later toalign with ext4's s_inode_readahead_blks behavior for slow devices too.""

    [1] git.kernel.org/torvalds/c/76a9

    #kernel #LinuxKernel

  14. Highlights from the main (used by ) merge for 6.17[1]:

    ""We now support metadata compression. It can be useful for embedded use cases or archiving a large number of small files.

    Additionally, readdir performance has been improved by enabling readahead (note that it was already common practice for ext3/4 non-dx and f2fs directories). We may consider further improvements later toalign with ext4's s_inode_readahead_blks behavior for slow devices too.""

    [1] git.kernel.org/torvalds/c/76a9

  15. Highlights from the main #erofs (used by #composefs) merge for #Linux 6.17[1]:

    ""We now support metadata compression. It can be useful for embedded use cases or archiving a large number of small files.

    Additionally, readdir performance has been improved by enabling readahead (note that it was already common practice for ext3/4 non-dx and f2fs directories). We may consider further improvements later toalign with ext4's s_inode_readahead_blks behavior for slow devices too.""

    [1] git.kernel.org/torvalds/c/76a9

    #kernel #LinuxKernel

  16. Highlights from the main #erofs (used by #composefs) merge for #Linux 6.17[1]:

    ""We now support metadata compression. It can be useful for embedded use cases or archiving a large number of small files.

    Additionally, readdir performance has been improved by enabling readahead (note that it was already common practice for ext3/4 non-dx and f2fs directories). We may consider further improvements later toalign with ext4's s_inode_readahead_blks behavior for slow devices too.""

    [1] git.kernel.org/torvalds/c/76a9

    #kernel #LinuxKernel

  17. Highlights from the main #erofs merge for #Linux 6.16 (git.kernel.org/torvalds/c/79b9):

    * a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.

    * Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.

    #kernel #LinuxKernel #Linux616 #filesystem

  18. Highlights from the main merge for 6.16 (git.kernel.org/torvalds/c/79b9):

    * a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.

    * Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.

  19. Highlights from the main #erofs merge for #Linux 6.16 (git.kernel.org/torvalds/c/79b9):

    * a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.

    * Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.

    #kernel #LinuxKernel #Linux616 #filesystem

  20. Highlights from the main #erofs merge for #Linux 6.16 (git.kernel.org/torvalds/c/79b9):

    * a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.

    * Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.

    #kernel #LinuxKernel #Linux616 #filesystem

  21. The new system call ()[1] after multiple revisions and various discussions[2] finally made it to -next and thus is slated to appear in 6.10:

    lore.kernel.org/all/2024041516

    [1] "In a nutshell, mseal() protects the VMAs of a given virtual memory range against modifications, such as changes to their permission bits."

    [2] lwn.net/Articles/948129/

  22. ""[…] In this article, we will do a deep dive into […] showing off #eBPF’s ability to poke deep within the #Linux #kernel internals to answer questions about the state of the running kernel.

    The subject of our investigation is #netfilter, […] Which of the rules in my firewall ruleset caused the drop of a particular packet?

    The goal of this article is to demonstrate how to answer this question. We can use this same approach to answer a myriad of questions about the kernel and to hook into pretty much any arbitrary point inside the kernel.""

    developers.redhat.com/articles (written by @toke)

    #LinuxKernel