Is there an eBPF equivalent for QNX?
Also, with the real-time linux patch (which has been mainlined now), I'm able to run C++ ROS2 control loops @ 1ms down to even 250us on commodity off the shelf i3 and i5 hardware with dedicated cores.
I've worked on vxWorks, QNX and Linux and I found the pace of development using Linux the fastest.
Wouldn't that not make sense for QNX? eBPF is for running code in kernel space but QNX is a microkernel. The microkernel approach would be to just run another userspace program like any other program.
Good point! I was look at it from a users pov. Let's say I have a BPF script for monitoring a set of processes - their disk, network and CPU with some filters on specific messages. Now can I use it in qnx or what's the equivalent? It can run in userspace for all I care.
This is about 25 yrs. back. As a grad student, I used to stumble into his papers pretty regularly. Later, I'd scan for author name and pay a lot more attention if it was by Arvind (also a few others). I'd always smile after looking at the author name. Growing up in India, your last name doesn't mean much.
> Growing up in India, your last name doesn't mean much.
My experience is the opposite. People often use only the last name, and first name is seldom used. E.g Mr. Kumaraswamy or Ms. Deshmukh in professional context and simply the last name in friend circles.
He probably means northern part of India. Surnames are more emphasised in the South than North.
I think it started when British started asking for surnames in job application in colonial India. South Indiana took their birthplace as surname along with caste name. In North, Singh and Kumar were used as surnames. Caste names became quite popular in late 20th century.
Before British, I am not sure if surnames were common anywhere in India. Would be a lovely study in history.
i think the reason people like arvind stopped using surnames was that, in india, surnames had come to mean far, far too much. now that he's dead he can't protest against mit news foisting a surname on him
S-Corp, W-2 for myself. I do pretty mundane programming related stuff for safety critical systems (med device and am always looking for interesting stuff). Been remote consulting averaging 1-2 clients since mid 2017. Here's my profile: https://www.linkedin.com/in/sriramsundar/. Worked full time for about 15 years prior.
Why do you think this? NYC, which spends extraordinary amounts of money on the NYPD, still only spends 10% of its budget on public safety[1]. The 4 largest categories are education (20%), transportation (15%), environmental protection (15%), and housing and economic development (15%).
There is some credence to the "make your own or shut up" argument here on HN.
If we reconsider your "criticize a restaurant" analogy, we are not random folks walking into a restaurant. We are professional chefs criticizing the output of other professional chefs.
In that context, "go start your own restaurant" does actually make sense.
Not every chef has the means (e.g. money and time) and/or non-food experience to start a restaurant. Constructive criticisms, and not all criticism is constructive, should always be taken in earnest; that said, there is also a matter of taste: just because one chef puts in extra garlic and another doesn't like that doesn't mean either is "wrong" or "right".
Lol, that's exactly how you get e.g. "Stupid food/we want plates" on reddit.
One of the worst things in computing is this sort of gatekeeping; it's not only "professional chefs" here, it's people who want to democratize more of software building, not reintroduce more silos.
Nice article! FTA: "One for one indicates that if a child crashes it, it and only it should be considered when restarting."
What is "it" in this context?
The one_for_one policy means that if a child process terminates, it will get restarted. It is appropriate when the child processes managed by the supervisor are (relatively) independent. The contrasting policy is one_for_all where a terminating child will also induce a restart of all the other children of the supervisor. This is appropriate when there's a number of important dependencies between the children processes, and you'd better just rebuild the whole subtree.
It is key to run the thought process of system failure. You need to understand what will happen if a certain part of your system errors out in an unforeseen way and make sure your restart policies are likely to right the ship.
> I already have ~20 pull requests pending and ready to go, but before we start the next merge frenzy, please give this final release one last round of testing, ok?
It means that Linux is holding off for a few days on starting the 6.6 release cycle, so that late issues can possibly be fixed before everyone's focus is captured again by the next release.
Usually that means awaiting the build results and self-tests from the distributions (although many will have already done that on the -rc kernels).
I've worked on vxWorks, QNX and Linux and I found the pace of development using Linux the fastest.