Take a look at Core Feature #2 in this post - https://deepflow.io/ebpf-the-key-technology-to-observability...
It looks like it's using tcp flow tuple + tcp_seq to join things.
954 karma · joined April 26, 2010
It looks like it's using tcp flow tuple + tcp_seq to join things.
BPF programs attached to syscalls (via kprobe or fentry) can read arguments via helpers (bpf_probe_read_{user,kernel}). Seccomp uses "classic BPF" which has no concept of helpers or calls.
> The currently available objective evidence is not sufficient to conclude whether or not there is a widespread public health concern related to servicing, including by third party servicers, of medical devices that would justify imposing additional/different, burdensome regulatory requirements at this time. Rather, the objective evidence indicates that many OEMs and third party entities provide high quality, safe, and effective servicing of medical devices.
https://www.fda.gov/media/113431/download
From my personal experience poking at a CPAP machine, there's nothing magical about it. All the sensors and active elements I could track down are available from the respective manufacturers in large quantities. The CPU is a freaking off the shelf STM32F4 with the jtag header still on the board. This is not some impossible to debug hyper-integrated design.
Still, it's not as tested as, say btrfs and ext4. Can't wait to see its particular quirks.
In particular, everything is compiled down to lookup tables and hash tables within each odex/oat. Your point still stands but the hit is much lower than you would think and given the slow speed of the superfluous reads, it ends up being a net positive for A LOT of cases.
1) fsync cost. Yes, fsyncs are dangerously slow in any Android app. (SQLite for example is a common culprit. Shared Prefs are another). HOWEVER, it's possible that flushes cause reads to be queued behind them (either in the kernel or on the device itself) which is even worse because
2) Random read cost is super super important. Android mmap's literally everything and demand paging is particularly common AND horrendous as a workflow. To add insult to injury, Android does not madvise the byte code or the resources as MADV_RANDOM, so read-ahead (or read-around) kicks in and you end up paging in 16KB-32KB where you only wanted 4KB.
Also, history has shown custom flash-based file system on Android to be a world of pain. yaffs, jffs have some pretty atrocious bugs/quirks. I'd much rather see the world unify on common file systems, optimized for flash-like storage, rather than OEMs shipping their own in-house broken file "systems" (I'm looking at you, Samsung).
I call bullshit. There's no reason Google can't update everything AOSP-y in /system - libc, libart, libwebkit etc.
> Google (and Apple and Microsoft) can totally do it for devices that manufactures and maintains on its own
That's a low bar. When you buy a Dell laptop, you continue to receive updates from Microsoft. This is the bar we should hold Google to.
As for the certification process, surely having one update that ships to N models is easier to test than N updates shipping to N models?
It's really fascinating stuff.
I sometimes wonder whether I should continue my education somewhere like Oxford, just so I can experience the focused concentration of a library again.
I'm completely in awe of the feedback loop here. It even compiles and swaps code while you're in the game!
In this business, the big competitors all reserve a bunch of rooms in the hotels and manage their booking themselves. The hotel is then not allowed to touch these rooms.
The model here was to give the hotels a reception-desk piece of software and have them use it to maintain availability. A lot of the hotels that signed up had nothing like this, so it was definitely a win for them. Armed with exact availability, you can have a much better booking system (and of course, if the hotel only wanted to give you a chunk of their rooms, they're perfectly capable of doing that).
Hotels can sign up on their own (including local bank details, etc) and just need to be reviewed before showing up on the site. It supports i18n, scheduled payments, lots of bells and whistles.
The fact of the matter is that this failed because of market reasons (too small a market, dominated by big players, primarily) but it may have a niche somewhere else on this planet. :)
Personally, I think there are some new-ish interesting immutability ideas that can be explored with regards to static files. It's not clear to me whether static assets (or even static sites) belong inside the container. I would be really interested in experienced folks' opinions on the immutability of the image. Where do you draw the line on what goes inside it and what's mounted in?
We've received really positive feedback from both hotels and tourists, it just turns out that Bulgaria is a really (really) tiny market.
The alternative is for the government to take down the entire game field.
PPTP is completely broken (MS-CHAPv2 especially), OpenVPN is hard to setup and maintain.
I've been using ssh as an impromptu VPN-like thing but I'd really, really like an actual VPN solution.
It's a laser-based solution, they're a small and lean team, their software is a Blender plugin and they sound competent. Also, did I mention the lasers?
What I'm saying is that you were right.
No one's making anyone communicate in a "lonely" way. If you don't like it, you are free to demand your preferred means of communication. What you'll find, however, is that people generally like it. "I tweet in my dreams," someone I know one said.
The truth of the matter is, constant communication is valuable. Not in the market cap type of way but as a type of human interaction. It matters to people. It helps them organize parties, revolutions, their lives around a stream of current data.
Is it distracting and addicting? Yes, it can be. But that's not a problem with the technology. If you lack the self-discipline to live in this deluge of information, guess what - help is one Google search away.
I guess my overall point is that the bandwidth of human communication has only ever been growing. It's not gonna stop now, so there's no point in longing for a long gone idyllic past.
P.S. I understand the hatred for dopamine triggers, wrapped in HTML. Meditation helps.
P.P.S. I'm making an assumption that people willfully choose a medium as a basis for discourse. That's not the case most of the time. I believe everyone should be made aware of how the medium they're using influences their thoughts and actions. I'm all up for having more media, though.
Also, many ATM cards (a foreign concept to this European until very recently) overlap with Visa ranges. In fact, my ATM card parses exactly as a Visa number. It even has the Visa trademark mentioned on the back. No, you can't use it for online transactions. Apparently, Visa Debit is not a thing in Canada ...
My point is, showing wrong UI is often worse than clunkier UI.
Nitpicking/design language question - would you use the term "affordance" to describe the avatar silhouette itself? To me, that's just a clue, an indicator, a hint to the general action possibility (affordance) of setting up an avatar.
It relies on a piece of kernel infrastructure called kexec-hardboot which to me sounds like black magic - it's like normal kexec but also resets all the peripherals so that they can be reinit by the new kernel. Magic.
Your use case should be accommodated too, granted, but it's not the direction they're currently headed.
It's a good book, is what I'm saying.