Ananyapam De’s Post

Operating systems (their kernel specifically) orchestrate many processes, allow access to memory, disk, network and execute processes by scheduling them to the CPU. Sounds simple when we put it this way but this task is vast. Writing efficient programs depends on how much understanding the engineer has in OS kernel. When we access a 32 bit integer in memory or write 6 bytes to disk, the kernel and hardware work together through several steps and layers to handle those tasks, simple as may seem. Each step and layer may add unpredictable costs. As a result we as engineers are bound to write inefficient code as we grind across the grain of the kernel. I built this course to demystify what I believe are the fundamentals operating systems to software engineers. By knowing how the kernel works, you will start writing software differently and naturally as you will start questioning what happens in each line you author. Like all my courses, I recommend the student having some programming experience to take this course, it just makes the course relatable. The course is focused on Linux but I do explain how Windows and Mac are different in certain situations. I hope you enjoy it. I'm happy I was able to finish it after 2 years of work. Use code "KERNEL" or head to https://lnkd.in/gWFufJA7

What do we mean when we say system is 32bit or 64 bit system ? ░▒▓█► ✿✿✿✿ 𝐂𝐒𝐄𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐚𝐥𝐬 ✿✿✿✿◄█▓▒░ A 32-bit or 64-bit system predominantly refers to the type of central processing unit (CPU), or processor, that a computer has. The bit designation is a measure of the size of the data types that it can handle, its memory limit, and the number and type of software programs it can run simultaneously. A 32-bit system can access 232 memory addresses, equating to 4 gigabytes of RAM, whereas a 64-bit can access 264 memory addresses, theoretically capable of handling 18.4 million terabytes of RAM. Because a 64-bit processor can handle more data at once - a larger number of wider 'bits' of data with each instruction cycle - it is usually faster than a 32-bit processor. Also, a 64-bit system can run both 32-bit and 64-bit software, while a 32-bit system can only run 32-bit software. Currently, most computers use 64-bit processors as they provide superior performance and can accommodate larger amounts of RAM, making them more suitable for memory-heavy applications like gaming, programming, or video editing. Ultimately, the bit designation reflects the computing capability of a system. In addition, in operating systems, the bit-degree indicates whether the system can use more or less physical memory. For instance, 32-bit versions of Windows can handle up to 4GB of memory, while 64-bit versions can manage up to 128GB or more, depending upon the version. 🆅🅸🆂🅸🆃 : https://lnkd.in/d3NzBDzE tgram grp : https://lnkd.in/gy93YX9 #programming #operatingsystem #systemprogramming #networking #linux #C/C++ #linux #datastructures #algorithms #sql #RDBMS #TCP #UDP #Router #loadbalancer #Coding #OOps #protocoldevelopment

𝗛𝗮𝗽𝗽𝘆 𝘁𝗼 𝘀𝗵𝗮𝗿𝗲 𝗺𝘆 𝘁𝗵𝗶𝗿𝗱 𝗹𝗲𝘀𝘀𝗼𝗻 𝗼𝗻 𝗟𝗶𝗻𝘂𝘅 𝗶𝗻 𝗖! 🎉🎉 Today, we're learning about threads. Threads let programs do many things at the same time. This is really good when we use a CPU with more than one core, but it's also useful if we have just one brain (CPU) in our SOC. 🎉 I've made some cool changes to our website too!🌟 Now, when you look at the lesson, you'll see colorful bits of code and a list of what's in the lesson a table of contents. It took me a little extra time to make these changes, so today's lesson is short but very interesting. 📖 https://lnkd.in/eEKJ5Tv7 I'm excited to share this with you. Let's learn together! 💻🌟 S.Tarik #threads #LearningLinux #embeddelinux #embeddedsystems #FunWithThreads #SimpleTechLesson

This week we talked about interrupts and I/O operations. https://lnkd.in/dhs9X8dX #interrupts #linux #kernel #pic #ports

RPI Pico – Target: DIY and Education – Mistakes The biggest mistake of RPI Pico is CMAKE, used for a handful of ARM code,   which leads to complex IDE integration... and wasted time.   - Example: #STM32 & #Microchip, the most used MCUs – they don’t even have builder automation & system, just code in a few folders. They can be easily integrated anywhere.   - Second example: #PlatformIO / #Arduino for ESP32 also failed due to the complex binding with CMAKE, which created other misunderstandings.   - Third example: #NuttX and others, which are much more complex than Pico SDK – they use MAKE ... for many MCUs and boards ! Second is the structuring of the SDK source code – folder/file... folder/file (for a handful of code),   which results in total chaos and complex assembly documentation that is still missing to this day.   The tools also include ones that have no place there. Third – constant compiling of tools and the lack of precompiled ones – a waste of time. Fourth – to work effectively, you need Linux, which limits users on Windows, who statistically make up the majority.  This issue stems from the above points. Fifth – mixing the SDK and poorly thought-out ecosystem adds additional problems. Sixth – the arrogant attitude of RPI towards the Embedded (software) Community. And so on...  According to them, that's the "right" way. But if the target is #DIY and education The question is: Who exactly are they educating? The grown-up kids?

Runc vs Crun in containers world: If you are some how into containerization technology, you might have heard about runc. Before I go into more details I would like to tell you what container exactly is. Containers mainly are created of two linux kernel modules; namespace and cgroup to create a jail like or isolated environment. Namespace: is used for what you can see or access Cgroup: is used for how much resources like RAM and CPU You can go on reading the full blog in https://lnkd.in/dVMWeim8

About to go to Microcenter... Configuring hardware is a b*tch- I need to get the software stuff started on my AI model for my Furby- My dude is on asshole mode when I asked for help like 5 times already(he is like look it up, I am like its mostly outdated resources and my GRUB configuration is off its sh*t for real on the BASH commands, so I can get my GPU working, might need to swap out the motherboard idk?) I got enough VRAM for a BERT model- FACEPALM! I am going to have their tech team brainstorm with me on how to trouble shoot #linux issues once we get this right- ( I am a team player...I hate when people dis me off to be a solo act...nothing is learned or gained from it. You know just flip me off...its more honest communications than being that way about it.) https://lnkd.in/gYUecSCr

Today's reading: 1.9 - Important Themes 1.9.2 - Concurrency and Parallelism C. Single-Instruction, Multiple-Data (SIMD) Parallelism "At the lowest level, many modern processors have special hardware that allows a single instruction to cause multiple operations to be performed in parallel, a mode known as single-instruction, multiple-data (SIMD) parallelism." 1.9.3 - The Importance of Abstractions in Computer Systems "The use of abstractions is one of the most important concepts in computer science...We have already been introduced to several of the abstractions seen in computer systems, as indicated in Figure 1.18. On the processor side, the instruction set architecture provides an abstraction of the actual processor hardware. With this abstraction, a machine code program behaves as if it were executed on a processor that performs just one instruction at a time. The underlying hardware is far more elaborate, executing multiple instructions in parallel, but always in a way that is consistent with the simple, sequential model. By keeping the same execution model, different processor implementations can execute the same machine code while offering a range of cost and performance." "On the operating system side, we have introduced three abstractions: files as an abstraction of I/O devices, virtual memory as an abstraction of program memory, and processes as an abstraction of a running program. To these abstractions we add a new one: the virtual machine, providing an abstraction of the entire computer, including the operating system, the processor, and the programs. The idea of a virtual machine was introduced by IBM in the 1960s, but it has become more prominent recently as a way to manage computers that must be able to run programs designed for multiple operating systems (such as Microsoft Windows, Mac OS X, and Linux) or different versions of the same operating system." #softwareengineer #computerscience #computersystems #aprogrammersperspective (https://lnkd.in/gbn-cvh5)

𝗬𝗼𝘂 𝘄𝗮𝗻𝘁 𝘁𝗼 𝗲𝘅𝘁𝗿𝗮𝗰𝘁 𝗶𝗻𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻 𝗼𝘂𝘁 𝗼𝗳 𝗣𝗗𝗙? ↳ OpenDataLab just dropped MinerU Demo: https://lnkd.in/eJCfyk8Z → Removes headers, footers, footnotes, and page numbers for 𝘀𝗲𝗺𝗮𝗻𝘁𝗶𝗰 𝗰𝗼𝗵𝗲𝗿𝗲𝗻𝗰𝗲.   → Outputs text in a 𝗵𝘂𝗺𝗮𝗻-𝗿𝗲𝗮𝗱𝗮𝗯𝗹𝗲 𝗼𝗿𝗱𝗲𝗿, fitting single-column, multi-column, and complex layouts.   → Preserves original document structure, including headings, paragraphs, and lists.   → Extracts 𝗶𝗺𝗮𝗴𝗲𝘀, descriptions, tables, and footnotes seamlessly.   → Converts formulas to 𝗟𝗮𝗧𝗲𝗫 format automatically.   → Supports OCR in 𝟴𝟰 𝗹𝗮𝗻𝗴𝘂𝗮𝗴𝗲𝘀 for broader accessibility.   → Offers multiple output formats like multimodal, NLP Markdown, and JSON sorted by reading order.   → Provides visualization results, including layout and span visualization for output quality checks.   → Works in both CPU and GPU environments.   → Compatible with Windows, Linux, and Mac platforms.  ⚠️ APGL license! Code: https://lnkd.in/eCxPVtvZ

📌 𝐓𝐡𝐞 𝐋𝐢𝐧𝐮𝐱 𝐁𝐨𝐨𝐭 𝐏𝐫𝐨𝐜𝐞𝐬𝐬 𝐢𝐧 8 𝐬𝐢𝐦𝐩𝐥𝐞 𝐬𝐭𝐞𝐩𝐬 - 𝐀𝐍 𝐈𝐍𝐓𝐄𝐑𝐕𝐈𝐄𝐖 𝐅𝐀𝐕𝐎𝐔𝐑𝐈𝐓𝐄 - - - 🟠 Step 1: Power On! Just like turning on a light, when you power up your computer, it kicks off a process called BIOS (Basic Input/Output System) or UEFI (Unified Extensible Firmware Interface). 🟠 Step 2: Checking the Essentials Next, the BIOS/UEEFI does a roll call of the computer's essentials - CPU, RAM, and storage devices. It's like checking if all players are present before starting a game! 🟠 Step 3: Picking the Boot Device Now, the computer needs to decide where to start the actual booting from. It could be the hard drive, a network server, or even a CD ROM. It's like choosing which door to open to enter a room. 🟠 Step 4: GRUB Time! Here comes GRUB (Grand Unified Bootloader). This is a friendly menu that lets you choose which operating system or specific settings you want to boot into. Think of it as a restaurant menu for your computer. 🟠 Step 5: Kernel & User Space Once you've made your choice, the kernel (core of the operating system) gets ready. Then, we switch to the user space where systemd, a kind of manager for the system, takes over. It sets up everything else like hardware and file systems. 🟠 Step 6: systemd In Charge systemd isn't just a manager; it's the default one that activates when the system boots. It ensures everything runs smoothly and other required components are started. 🟠 Step 7: Running Startup Scripts Now, the system runs a series of startup scripts. These are like instructions to set up and configure the environment. 🟠 Step 8: Ready to Log In! Finally, you'll see the login window, Welcome! And there you have it - from a quiet machine to a fully operational system, ready for your commands. #linux #devops #interviewtips