LWN.net's Journal
[Most Recent Entries]
[Calendar View]
Thursday, January 3rd, 2019
| Time |
Event |
| 1:36a |
[$] LWN.net Weekly Edition for January 3, 2019
The LWN.net Weekly Edition for January 3, 2019 is available. | | 2:53p |
Cuni: PyPy for low-latency systems Antonio Cuni writes
about recent work to support running Python code with low latency requirements under PyPy. " As we said, the total cost of memory
management is less on PyPy than on CPython, and it's one of the reasons why
PyPy is so fast. However, one big disadvantage is that while on CPython the
cost of memory management is spread all over the execution of the program,
on PyPy it is concentrated into GC runs, causing observable pauses which
interrupt the execution of the user program. To avoid excessively long
pauses, the PyPy GC has been using an incremental strategy since 2013. The
GC runs as a series of 'steps', letting the user program to progress
between each step." | | 3:11p |
LWN emails bouncing due to dnsbl.njabl.org There are currently a number of sites bouncing emails from LWN.net due to an alleged listing in the dnsbl.njabl.org blacklist. The only problem is that this blacklist has
been offline since 2013. That domain has been taken over by somebody else; checking web content at that address is not recommended as it is, to put it lightly, non-technical. If you are not getting expected email from LWN, you might want to look into whether your local setup is still trying to use that old, discontinued blacklist. | | 3:21p |
Security updates for Thursday
Security updates have been issued by Debian (jasper, libdatetime-timezone-perl, qtbase-opensource-src, thunderbird, and tzdata), Red Hat (rh-perl524-perl), and SUSE (libraw, polkit, and xen). | | 5:43p |
[$] A setback for fs-verity The fs-verity mechanism, created to protect files on Android devices from hostile modification by attackers, seemed to be on track for inclusion into the mainline kernel during the current merge window when the
patch set was posted at the beginning of November. Indeed, it wasn't until mid-December that some other developers started to raise objections. The resulting conversation has revealed a deep difference of opinion regarding what makes a good filesystem-related API and may have implications for how similar features are implemented in the future. |
|