rzezeski

5 ms·

1.
by rzezeski 3y ago
I wrote a detailed walk-through of the illumos syscall handler back in 2016. It's missing the updates around KPTI (meltdown mitigation), but other than that the mechanisms should be unchanged. https://zinascii.com/2016&
2.
by rzezeski 5y ago
Probably more to do with the fact that everything is moving towards virtualization. Oftentimes these NICs dole out VFs directly to VMs via SR-IOV, in which case I imagine the NIC controller has some safeguards to keep the host and the rest
3.
by rzezeski 5y ago
> During those tests, we noticed the machines were randomly freezing after some time, so we decided to upgrade the firmware of the network cards, Reminds me of the various i40e Tx freezes I debugged while at Joyent. Granted, this is the
4.
by rzezeski 7y ago
You just figured it out.
5.
Notes on the History of Fork and Join(ieeexplore.ieee.org)
3 points by rzezeski 10y ago|0 comments
6.
by rzezeski 12y ago
That's a good question. I should have mentioned that in the post perhaps. The reason I initially ran vmstat was just to make sure my dev machine was "zeroed out". Recently my kernel builds had taken twice the time as norma
7.
How My Printer Caused Excessive Syscalls and UDP Traffic(zinascii.com)
90 points by rzezeski 12y ago|16 comments
8.
by rzezeski 12y ago
According to POSIX.1b RT signals are used for other features defined in .1b. An excerpt from "POSIX.4 Programmers Guide": > So far, we've talked about real-time signals sent by the sigqueue function. However, most POSIX.4
9.
by rzezeski 12y ago
All kernels do not use the same libc. In fact, Linux is different in the fact that it doesn't ship a libc with the kernel. Illumos, the OS I investigated, goes by the philosophy that you _have_ to ship libc with your kernel, and thus
10.
Most operating systems have implemented realtime signals incorrectly(zinascii.com)
105 points by rzezeski 12y ago|23 comments
11.
by rzezeski 12y ago
Author here, I won't get to it today but I would like to try the method you describe. I realize that benchmarking is a very tricky thing having followed Brendan Gregg's work the last couple of years. This is why I also ran my ba
12.
by rzezeski 12y ago
Hi, author here. My align_2 implementation is indeed very naive. Part of that was to show just how much overhead a naive implementation could add, in this case 3 orders of magnitude. I'm also new to systems programming. This articl
13.
The 8-Byte Two-Step(zinascii.com)
48 points by rzezeski 12y ago|31 comments
14.
A Posix Queue Implementation(zinascii.com)
88 points by rzezeski 12y ago|13 comments
15.
by rzezeski 12y ago
Not only that, why make every user reimplement the same resolution strategies? Or make Basho dev's reimplement them for each official client? You'll increase the chance for bugs or subtle semantic differences. Also, many users
16.
by rzezeski 15y ago
There may be more to the situation. I wonder if Normalcy Bias also played a role in Air France 447.
17.
by rzezeski 15y ago
Replicas (or as you put it, ring replication) is critical, and Riak very much has replicas. What it doesn't have in it's open source version is multi-ring replication (cross DC) which is a separate concern. In the Dynamo paper the ring spa
18.
by rzezeski 15y ago
I agree in general with the sentiment but don't like rule of an absolute # of slides. To this day one of the best presentations I've ever seen had 500+ slides and is an example of what a good presentation looks/feels like. http://www.info
19.
by rzezeski 15y ago
I work at Basho. Specifically I've been doing a lot of work on Riak Search lately. I absolutely agree that the Search documentation is underwhelming and could use some major love. I take it as a personal challenge to improve the situatio
20.
by rzezeski 15y ago
If we are talking about performing range queries on an index then Riak already has it in the form of Riak Search. In 1.0 this is also supported by secondary indices. If we are talking about performing a range operation on the primary key w
21.
by rzezeski 15y ago
I know nothing about Switft so I'll keep my comments strictly related to Luwak. Luwak preforms really well as a large object store...up to a point. I've personally seen latencies of < 4s when writing/reading a 700+MB CSV across 3 physi
22.
by rzezeski 16y ago
You are performing a GET for the same key each time? Don't quote me on this but I took a quick glance at the code and it looks like all gets are [currently] serialized at the vnode level. Since your key will always hash to the same vnodes