PostgreSQL 11: something for everyone [LWN.net]
Please consider subscribing to LWNSubscriptions are the lifeblood of LWN.net. If you appreciate this content and would like to see more of it, your subscription will help to ensure that LWN continues to thrive. Please visit this page to join up and keep LWN on the net. PostgreSQL 11 had its third beta release on August 9; a fourth beta (or possibly a release candidate) is scheduled for mid-Septemb
A reworked TCP zero-copy receive API [LWN.net]
LWN.net needs you!Without subscribers, LWN would simply not exist. Please consider signing up for a subscription and helping to keep LWN publishing In April, LWN looked at the new API for zero-copy reception of TCP data that had been merged into the net-next tree for the 4.18 development cycle. After that article was written, a couple of issues came to the fore that required some changes to the AP
nproc: netlink access to /proc information
Albert Cahalan <albert@users.sf.net>, William Lee Irwin III <wli@holomorphy.com>, "Martin J. Bligh" <mbligh@aracnet.com>, Paul Jackson <pj@sgi.com> [ Cc: contributors to recent, related thread ] nproc is an attempt to address the current problems with /proc. In short, it exposes the same information via netlink (implemented for a small subset). This patch is experimental. I'm posting it to get the
kernel: add a netlink interface to get information about processes (v2) [LWN.net]
linux-api@vger.kernel.org, Andrey Vagin <avagin@openvz.org>, Oleg Nesterov <oleg@redhat.com>, Andrew Morton <akpm@linux-foundation.org>, Cyrill Gorcunov <gorcunov@openvz.org>, Pavel Emelyanov <xemul@parallels.com>, Roger Luethi <rl@hellgate.ch>, Arnd Bergmann <arnd@arndb.de>, Arnaldo Carvalho de Melo <acme@kernel.org>, David Ahern <dsahern@gmail.com>, Andy Lutomirski <luto@amacapital.net>, Pavel O
Software interrupts and realtime [LWN.net]
Did you know...?LWN.net is a subscriber-supported publication; we rely on subscribers to keep the entire operation going. Please help out by buying a subscription and keeping LWN on the net. The Linux kernel's software interrupt ("softirq") mechanism is a bit of a strange beast. It is an obscure holdover from the earliest days of Linux and a mechanism that few kernel developers ever deal with dire
The TCP "challenge ACK" side channel [LWN.net]
Did you know...?LWN.net is a subscriber-supported publication; we rely on subscribers to keep the entire operation going. Please help out by buying a subscription and keeping LWN on the net. Side-channel attacks against various kinds of protocols (typically networking or cryptographic) are both dangerous and often hard for developers and reviewers to spot. They are generally passive attacks, which
General unprivileged mount support [LWN.net]
Linux Containers <containers@lists.linux-foundation.org>, <linux-fsdevel@vger.kernel.org>, Linux API <linux-api@vger.kernel.org>, James Bottomley <James.Bottomley@HansenPartnership.com>, Djalal Harouni <tixxdz@gmail.com>, "Serge E. Hallyn" <serge@hallyn.com>, Andy Lutomirski <luto@amacapital.net>, Jan Kara <jack@suse.cz>, Jann Horn <jannh@google.com>, Michael Kerrisk <mtk.manpages@gmail.com> As we
Present useful limits to user [LWN.net]
Hello, There are many basic ways to control processes, including capabilities, cgroups and resource limits. However, there are far fewer ways to find out useful values for the limits, except blind trial and error. This patch series attempts to fix that by giving at least a nice starting point from the actual maximum values. I looked where each limit is checked and added a call to limit bump nearby
namespaces: add transparent user namespaces [LWN.net]
This allows the admin of a user namespace to mark the namespace as transparent. All other namespaces, by default, are opaque. While the current behavior of user namespaces is appropriate for use in containers, there are many programs that only use user namespaces because doing so enables them to do other things (e.g. unsharing the mount or network namespace) that require namespaced capabilities. F
shiftfs: uid/gid shifting filesystem [LWN.net]
This is currently an RFC because the patch applies to Linus head, but needs altering for the vfs tree, so I'll respin and resend after the merge window closes. My use case for this is that I run a lot of unprivileged architectural emulation containers on my system using user namespaces. Details here: http://blog.hansenpartnership.com/unprivileged-build-cont... They're mostly for building non-x86 s
/dev/random - a new approach [LWN.net]
Hi Herbert, Ted, The venerable Linux /dev/random served users of cryptographic mechanisms well for a long time. Its behavior is well understood to deliver entropic data. In the last years, however, the Linux /dev/random showed signs of age where it has challenges to cope with modern computing environments ranging from tiny embedded systems, over new hardware resources such as SSDs, up to massive p
Namespaces in operation, part 4: more on PID namespaces [LWN.net]
Namespaces in operation, part 4: more on PID namespaces This article brought to you by LWN subscribersSubscribers to LWN.net made this article — and everything that surrounds it — possible. If you appreciate our content, please buy a subscription and make the next set of articles possible. In this article, we continue last week's discussion of PID namespaces (and extend our ongoing series on names
![Namespaces in operation, part 4: more on PID namespaces [LWN.net]](https://cdn-ak-scissors.b.st-hatena.com/image/square/ec98d0440882a88c05cbacf47e85a564b9078135/height=288;version=1;width=512/https%3A%2F%2Fstatic.lwn.net%2Fimages%2F2013%2Fnamespaces%2Fpidns_orphan_1.png)
epoll: add EPOLLEXCLUSIVE flag [LWN.net]
<e26b962fcb6f87a81b38d5dc812cf33fd7549c8a.1449523436.git.jbaron@akamai.com> mingo@kernel.org, peterz@infradead.org, viro@ftp.linux.org.uk, mtk.manpages@gmail.com, normalperson@yhbt.net, m@silodev.com, corbet@lwn.net, luto@amacapital.net, torvalds@linux-foundation.org, hagen@jauu.net, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org Currently, epoll file descri
copy_file_range() [LWN.net]
LWN.net needs you!Without subscribers, LWN would simply not exist. Please consider signing up for a subscription and helping to keep LWN publishing Computers tend to spend a lot of time copying files. Often, the underlying filesystems have ways to accelerate that task, but, as a general rule, copying is still done with a user-space loop reading chunks of data from one file and writing to another.
TCP small queues [LWN.net]
Please consider subscribing to LWNSubscriptions are the lifeblood of LWN.net. If you appreciate this content and would like to see more of it, your subscription will help to ensure that LWN continues to thrive. Please visit this page to join up and keep LWN on the net. The "bufferbloat" problem is the result of excessive buffering in the network stack; it leads to long latencies and poor reliabili
mutex: implement adaptive spinning [LWN.net]
Ingo Molnar <mingo@elte.hu>, "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>, Gregory Haskins <ghaskins@novell.com>, Matthew Wilcox <matthew@wil.cx>, Andi Kleen <andi@firstfloor.org>, Chris Mason <chris.mason@oracle.com>, Andrew Morton <akpm@linux-foundation.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, linux-fsdevel <linux-fsdevel@vger.kernel.org>, linux-btrfs <linux-btrfs@vger.
Huge pages part 1 (Introduction) [LWN.net]
Please consider subscribing to LWNSubscriptions are the lifeblood of LWN.net. If you appreciate this content and would like to see more of it, your subscription will help to ensure that LWN continues to thrive. Please visit this page to join up and keep LWN on the net. [Editor's note: this article is the first in a five-part series on the use of huge pages with Linux. We are most fortunate to have
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Network namespaces [LWN.net]
Paravirtualized ticket spinlocks [LWN.net]
Linux 4.6 is out [LWN.net]