Skip to content
View mcastelino's full-sized avatar
Block or Report

Block or report mcastelino

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned

  1. ciao ciao Public

    Forked from ciao-project/ciao

    Ciao - Cloud Integrated Advanced Orchestrator

    Go

  2. ikgt-core ikgt-core Public

    Forked from intel/ikgt-core

    Intel Kernel Guard Technology Core Repo

    C

  3. iptables-cheatsheet iptables-cheatsheet
    1
    
                  
    2
    The netfilter hooks in the kernel and where they hook in the packet flow
    3
    ------------------------------------------------------------------------
    4
    
                  
    5
    The figure below calls out
  4. Tracing QEMU-KVM Interactions Tracing QEMU-KVM Interactions
    1
    # Tracing QEMU-KVM Interactions
    2
    
                  
    3
    But default in linux you can figure out how many times and for what reasons there is a VM Exit from a VM into the kvm kernel module.
    4
    However given the ubiquity of vhost and the ability of kvm to emulate most device models directly in the kernel, most of those VM exits do not result in a transition from host kernel into the QEMU. The transitions from VM -> kvm -> QEMU are typically the most expensive.
    5
    
                  
  5. Footloose as a Kubernetes POD. So a ... Footloose as a Kubernetes POD. So a VM in Kubernetes launched and managed as a container using the Kata runtimeClass.
    1
    # Footloose as a Kubernetes POD. So a VM in Kubernetes launched and managed as a container using the Kata runtimeClass.
    2
    
                  
    3
    ```yaml
    4
    apiVersion: v1
    5
    data:
  6. Kubernetes and cgroups Resource Mana... Kubernetes and cgroups Resource Management/Static cpuManagerPolicy/Memory and Resource Isolation & Scheduling
    1
    # Overview
    2
    
                  
    3
    The goal of this document to cover all aspects of Kubernetes management, including how resources are expressed, constrained and accounted for. This started a way to ensure that alternate container runtime implementation like Kata containers will behave from a resource accounting and consumption point of view in the same manner as `runc`.
    4
    
                  
    5
    Location of the latest version of this document: https://gist.github.com/mcastelino/b8ce9a70b00ee56036dadd70ded53e9f