AV1 Image File Format (AVIF), Awful Intel Standards, and Linux Kernel at LWN


-
AV1 Image File Format v1.0 Finalized
The AV1 Image File Format (AVIF) appears solid now with it having been promoted to version 1.0.0.
The AV1 Image File Format (AVIF) is the specification for storing images and image sequences (animated images) compressed via AV1 in the HEIF High-Efficiency Image File Format. AV1, of course, being the promising royalty-free video coding format competing with the likes of HEVC/H.265. This is to AV1 as the WebP image format is to VP9/WebM.
The AV1 Image File Format continues making inroads and being worked on by the likes of Netflix and Microsoft, among other tech companies. Back in December, Netflix began publishing sample AVIF sample images here.
-
USB 3.2 Is Here To Make Things More Confusing For Everyone
But with the introduction of USB 3.2, things have become even more confusing.
The USB standards body has now rebranded 5Gb/s devices as “USB 3.2 Gen 1,” 10Gb/s devices as “USB 3.2 Gen 2” and the latest standard offering 20Gb/s speed has been dubbed “USB 3.2 Gen 2×2” because two 10Gb/s connections run parallelly in the wire.
-
The Intel-Developed Vulkan Overlay Layer Picks Up New Features, Dump FPS To File
It was just one week ago that developers from the Intel Open-Source Technology Center contributed their new Vulkan Overlay later to Mesa 19.1 for providing various performance metrics/statistics of use to application/driver developers. This Vulkan overlay continues being improved upon as well as making it more applicable to gamers/enthusiasts.
-
The case of the supersized shebang
Regressions are an unavoidable side effect of software development; the kernel is no different in that regard. The 5.0 kernel introduced a change in the handling of the "#!" (or "shebang") lines used to indicate which interpreter should handle an executable text file. The problem has been duly fixed, but the incident shows how easy it can be to introduce unexpected problems and highlights some areas where the kernel's development process does not work as well as we might like.
By longstanding Unix convention, an attempt to execute a file that does not have a recognized binary format will result in that file being passed to an interpreter. By default, the interpreter is a shell, which will interpret the file as a shell script. If, however, the file starts with the characters "#!", the remainder of the first line will be treated as the name of the interpreter to use (and possibly arguments to be passed to that interpreter). This mechanism allows programs written in almost any interpreted language to be executed directly; the user need never know which interpreter is actually doing the work behind the scenes. -
Per-vector software-interrupt masking
Software interrupts (or "softirqs") are one of the oldest deferred-execution mechanisms in the kernel, and that age shows at times. Some developers have been occasionally heard to mutter about removing them, but softirqs are too deeply embedded into how the kernel works to be easily ripped out; most developers just leave them alone. So the recent per-vector softirq masking patch set from Frederic Weisbecker is noteworthy as an exception to that rule. Weisbecker is not getting rid of softirqs, but he is trying to reduce their impact and improve their latency.
Hardware interrupts are the means by which the hardware can gain a CPU's attention to signal the completion of an I/O operation or some other situation of interest. When an interrupt is raised, the currently running code is (usually) preempted and an interrupt handler within the kernel is executed. A cardinal rule for interrupt handlers is that they must execute quickly, since they interfere with the other work the CPU is meant to be doing. That usually implies that an interrupt handler will do little more than acknowledge the interrupt to the hardware and set aside enough information to allow the real processing work to be done in a lower-priority mode.The kernel offers a number of deferred-execution mechanisms through which that work can eventually be done. In current kernels, the most commonly used of those is workqueues, which can be used to queue a function call to be run in kernel-thread context at some later time. Another is tasklets, which execute at a higher priority than workqueues; adding new tasklet users tends to be mildly discouraged for reasons we'll get to. Other kernel subsystems might use timers or dedicated kernel threads to get their deferred work done.
-

- Login or register to post comments
Printer-friendly version- 6170 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is released
After three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release.
|
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future Tech
The metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world.
Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility.
|
today's howtos
|








.svg_.png)
Content (where original) is available under CC-BY-SA, copyrighted by original author/s.

Recent comments
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago