TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Bus1: a new Linux interprocess communication proposal

46 点作者 b3h3moth超过 8 年前

4 条评论

philips超过 8 年前
Previous discussion: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=12309590" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=12309590</a>
评论 #12365069 未加载
Aissen超过 8 年前
Discussions from last week: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=12309590" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=12309590</a><p>Not that there was anything constructive, since most people did not read the article &amp; ksummit email.
评论 #12359606 未加载
评论 #12359251 未加载
评论 #12359427 未加载
nullspace超过 8 年前
I&#x27;m not a kernel engineer or an operating systems engineer so this may be a naive question. This line was confusing to me:<p>&gt; This is achieved using local clocks at each peer that are synchronized in a manner similar to that used for Lamport clocks.<p>From Linux&#x27;s perspective, it&#x27;s just running on one machine with one system &#x2F; module that determines the time of the machine right? Why do two peers need to have their local logical clock?<p>From my understanding, clocks are a problem for distributed systems that can&#x27;t share a single clock without significant latency and loss of availability. Why is this a problem for Linux as well?
api超过 8 年前
Part of the reason OS IPC is stagnant is that it&#x27;s not that interesting or useful.<p>I feel like the folks making these and other (kdbus) proposals are still thinking in terms of a &quot;box.&quot; Boxes are dying. Almost everything interesting these days is distributed across networks with boxes being mere commodity hosts.<p>This is true in any modern data center or cloud infrastructure, and here it&#x27;s often done via things like Kubernetes plus a pub sub bus and a clustered database.<p>It&#x27;s also IMHO going to be true of any future next generation &quot;decentralized&quot; personal computing platform. All the interesting work I see in that space also takes the form of distributed systems that try to abstract away the box and deliver a kind of formless global cloud where boundaries are cryptographic.<p>In both cases the box is dying because it is unreliable and doesn&#x27;t scale.<p>The trouble with local IPC is that its APIs are not going to be the same as network IPC. As a result programmers have to think about local vs remote to make use of it. So they won&#x27;t.<p>That leaves only the local system services use case, which is already served.
评论 #12359426 未加载
评论 #12359526 未加载
评论 #12359586 未加载