int0x80

10 ms·

61.
by int0x80 8y ago
I agree with this thoughts very much. The attitude you mention is key, at least in my reduced and anecdotical experience. It is true, however, as others say, that you have to start from a reasonable and relative good baseline and that part
62.
by int0x80 8y ago
For a subset of "ASCII art" diagrams, check http://asciiflow.com I find it handy sometimes :)
63.
by int0x80 8y ago
IA32 is probably not getting all the focus from devs and users this days, still surprising whoever... Do you have a link to the issue, out of curiosity?
64.
by int0x80 8y ago
This is not primary about static checking. This is mostly a guarantee to the implementation so it has information at the target function so it can generate better code without having to resort to derivations or complex data flows (to optimi
65.
by int0x80 8y ago
One way is to over-allocate in the first place. When your spare pool is draining below a watermark, you scale in. Hopefuly there is enough time for that scale event to complete before the pool drains completely.
66.
by int0x80 8y ago
Any reference to this "holy grail" problem?
67.
by int0x80 8y ago
To me this is 'just' an optimization. If sorting by ID means 'sort by creation time' then you are just optimizing a timestamp in an entity. Overloading the ID, IOW. For the 'create the ID in the app' yes, but t
68.
by int0x80 8y ago
I agree here. But they just want to cover their asses I guess.
69.
by int0x80 8y ago
Yeah.. I think I see what you say, I mean, the end user interface is the quite the same but this has big implications anyway for the systems design POV, so is not a small thing :)
70.
by int0x80 8y ago
That is one big difference, with big implications.
71.
by int0x80 8y ago
With LUKS it doesn't matter. But not all encryption methods are like that. That was just really an example of potential differences. In fact, when this (Dropbox dropping non ext4 support) happened the problem that triggered this was en
72.
by int0x80 8y ago
In principle I agree with you, and many could argue the the app is broken. But in all fairness it is not so easy. Then there are lots of little details and corner cases where filesystems that implement a POSIX fs have slightly different sem
73.
by int0x80 8y ago
It's not profitable /or/ you are just going for the short-term and easy way out of the problem.
74.
by int0x80 8y ago
That code sample is outright ridiculous, it is totaly out of control. Can't agree more.
75.
by int0x80 8y ago
>Python has smoother installation than Java and GCC How so? With java you can get your distro version from the package manager or just download a tarball and setup your PATH. Maybe install maven. GCC and build deps is as simple as a xxx
76.
by int0x80 8y ago
There is mmap for read/write (some of the most used syscalls). There is also the vdso page [1] for things like gettimeofday etc. [1] http://man7.org/linux/man-pages/man7/vdso.7.html
77.
by int0x80 8y ago
It is possible. As you say, not completely problem free and indeed has raised some discussions regarding security implications. AFAICT documentation is scarce (non-existent). Here is a previous patch prepping for this one, with sample code
78.
by int0x80 8y ago
Yes. Instead of using a syscall to get/issue events you use a mapped ring buffer. See https://lwn.net/Articles/743714/
79.
by int0x80 8y ago
The kernel handles the IO. You just don't need to enter the kernel (syscall) to issue it, it is done via a kernel<->user memory mapped ring buffer. Roughly, I don't really know the details well. See https://lwn.ne
80.
by int0x80 8y ago
Both?
81.
by int0x80 8y ago
I think an 'error out if overflow/truncation'-mode available as a command line flag could be useful if you just don't have any JS involved in the JSON pipeline.
82.
by int0x80 8y ago
It makes sense (to me) and it has been discussed. I don't know what was the conclusion though.
83.
by int0x80 8y ago
Maybe. But KGDB and friends do exist too in Linux. And (AFAIK) not everyone likes using those, some just like throwing a few printks here and there. That is not universal obviously :) My point is that yes, unikernels may not be as easy to d
84.
by int0x80 8y ago
That an also to avoid posibly revealing internals and details of the designs/architecture/etc to non-intel people.
85.
by int0x80 8y ago
Exactly my thoughts :) Also: the F22 datalinks are incompatible and can not easily interoperate with the F35 ones. That problem sound familiar too.
86.
by int0x80 8y ago
I think that can be solved by good tracing and logging facilities. Both of which are already available in Linux (eBPF, ftrace, tracepoints, perf events...). You may have to customize them or polish them further though and provide more user
87.
by int0x80 8y ago
It might be wrong though, even if common. That might explain a few things in fact.
88.
by int0x80 8y ago
Ahh sorry, I understood the other way around :)
89.
by int0x80 8y ago
They can do right now. Both the API and ABI are very rarely (read never but very problematic bugs or similar) broken in a backwards way.
90.
by int0x80 8y ago
I was talking about the italian pronuntiation.

More ›