ioxide.Kestrel 0.0.16

dotnet add package ioxide.Kestrel --version 0.0.16
                    
NuGet\Install-Package ioxide.Kestrel -Version 0.0.16
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="ioxide.Kestrel" Version="0.0.16" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="ioxide.Kestrel" Version="0.0.16" />
                    
Directory.Packages.props
<PackageReference Include="ioxide.Kestrel" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add ioxide.Kestrel --version 0.0.16
                    
#r "nuget: ioxide.Kestrel, 0.0.16"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package ioxide.Kestrel@0.0.16
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=ioxide.Kestrel&version=0.0.16
                    
Install as a Cake Addin
#tool nuget:?package=ioxide.Kestrel&version=0.0.16
                    
Install as a Cake Tool

ioxide.Kestrel

An ASP.NET Core Kestrel transport backed by the ioxide io_uring runtime. One reactor (io_uring ring) per core, SO_REUSEPORT load-balanced, with Kestrel's entire request loop pinned to the reactor thread — no ThreadPool hop on the hot path.

Usage

var builder = WebApplication.CreateBuilder(args);

builder.WebHost.UseIoxide();   // replaces Kestrel's default sockets transport

var app = builder.Build();
app.MapGet("/", () => "Hello, World!");
app.Run();

Options:

builder.WebHost.UseIoxide(o =>
{
    o.ReactorCount = Environment.ProcessorCount;          // rings/threads (default: ProcessorCount)
    o.ConfigureServer = cfg => cfg with { RingEntries = 8192 };   // tune the underlying ioxide ServerConfig
});

How it works

Each accepted connection is bridged to Kestrel through a System.IO.Pipelines duplex whose reader schedulers route continuations onto the owning reactor thread. A recv pump copies received bytes into the inbound pipe and a send pump drains Kestrel's response into the connection's send slab, so recv → HTTP parse → handler → send all run on a single ring thread.

Requirements

  • Linux with io_uring (kernel 6.x recommended).
  • .NET 11.

Inline execution note: like any thread-per-core transport, application middleware runs on the reactor thread. Blocking work in a handler stalls every connection on that reactor — keep handlers async.

Product Compatible and additional computed target framework versions.
.NET net11.0 is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.0.16 24 6/21/2026
0.0.15 28 6/21/2026
0.0.14 40 6/21/2026
0.0.13 46 6/21/2026