live wire
▸SECURITY · Red Hat rates the OpenShift AI 3.4.6 update CriticalRed Hat advisory▸SECURITY · Quarkus ships emergency 3.33.4.2 and 3.40.1.2 LTS fixes for management auth bypass and Brotli RCEQuarkus▸OpenShift 5 adds GA update risk checks and troubleshooting, with agentic updates and autonomous fixes in previewRed Hat▸SUPPLY CHAIN · IBM plans Claude Mythos scanning in Concert Protect with Red Hat Lightwell remediationIBM▸SECURITY — OpenShift 5 and RHACS 5 add confidential GPU, KEV prioritization and AI model signing controlsRed Hat▸PLATFORM · OpenShift 5 reaches ROSA with hosted control planes and agentic troubleshootingRed Hat▸PLATFORM · OpenShift 5 extends standard support to two years and designates five-year ELC releasesRed Hat▸AI · Red Hat says EnMaaS shifted 70% of engineering traffic to self-hosted open modelsRed Hat▸DEVELOPER HUB · Developer Hub 2.1 adds MCP actions, AI asset catalogs and a 10-month support windowRed Hat▸PLATFORM · RHEL 10.3 and 9.9 add sealed bootc images, governed MCP diagnostics and self-hosted AI helpRed Hat▸DEVELOPER HUB · Red Hat adds opt-in screen and DOM context to Developer Hub’s intelligent assistantRed Hat Developer▸PLATFORM · OpenShift 5 reaches GA with MCP controls, GPU DRA and a rebuilt developer stackRed Hat Developer▸PLATFORM · Red Hat Edge Manager 1.3.2 adds standalone deployment alongside RHACM and Ansible pluginsRed Hat Product Errata▸SECURITY · OpenShift 4.18.60 fixes unverified remote inventory script executionRed Hat Product Security▸SECURITY · Red Hat rates the OpenShift AI 3.4.6 update CriticalRed Hat advisory▸SECURITY · Quarkus ships emergency 3.33.4.2 and 3.40.1.2 LTS fixes for management auth bypass and Brotli RCEQuarkus▸OpenShift 5 adds GA update risk checks and troubleshooting, with agentic updates and autonomous fixes in previewRed Hat▸SUPPLY CHAIN · IBM plans Claude Mythos scanning in Concert Protect with Red Hat Lightwell remediationIBM▸SECURITY — OpenShift 5 and RHACS 5 add confidential GPU, KEV prioritization and AI model signing controlsRed Hat▸PLATFORM · OpenShift 5 reaches ROSA with hosted control planes and agentic troubleshootingRed Hat▸PLATFORM · OpenShift 5 extends standard support to two years and designates five-year ELC releasesRed Hat▸AI · Red Hat says EnMaaS shifted 70% of engineering traffic to self-hosted open modelsRed Hat▸DEVELOPER HUB · Developer Hub 2.1 adds MCP actions, AI asset catalogs and a 10-month support windowRed Hat▸PLATFORM · RHEL 10.3 and 9.9 add sealed bootc images, governed MCP diagnostics and self-hosted AI helpRed Hat▸DEVELOPER HUB · Red Hat adds opt-in screen and DOM context to Developer Hub’s intelligent assistantRed Hat Developer▸PLATFORM · OpenShift 5 reaches GA with MCP controls, GPU DRA and a rebuilt developer stackRed Hat Developer▸PLATFORM · Red Hat Edge Manager 1.3.2 adds standalone deployment alongside RHACM and Ansible pluginsRed Hat Product Errata▸SECURITY · OpenShift 4.18.60 fixes unverified remote inventory script executionRed Hat Product Security
upstreambeat.ai
newsAI

vLLM-backed kernel alignment stabilizes asynchronous reinforcement learning

REINFORCE Zero separates numerical kernel mismatch from policy-weight lag, then uses unclipped importance sampling to train asynchronously without rejection gates.

By The News Desk· Nov 7, 2026the quick take — two AI hosts go live when you do

Asynchronous reinforcement learning promises better hardware utilization by letting model rollout and optimization run at the same time. Its weakness is that the learner trains on samples produced by older model weights—and, in practice, by kernels that can calculate slightly different token probabilities from the training stack.

A new engineering report from the vLLM community says those are separate problems and should be treated separately. REINFORCE Zero, developed by NVIDIA Research and Inferact contributors, aligns rollout and learner kernels so they produce bitwise-identical token probabilities at the same weights. It then uses ordinary, unclipped token-level importance sampling to correct the remaining lag between the older rollout policy and the current learner.

What changed

The approach removes sample-rejection gates and clipping from the core recipe. Rollout records the probability of each sampled token; the learner divides its current probability by that recorded value and uses the ratio directly. With the numerical mismatch removed first, the authors report that the remaining weight-lag correction changes smoothly enough for training to remain stable.

The paper and open repository report stable runs through 20,000 policy updates. On 16 GPUs over 12,000 updates, asynchronous training completed in 68.55 training-step hours versus 164.77 hours for synchronous training with aligned kernels—a reported 2.40× throughput improvement with comparable reasoning quality. A Qwen3-4B tool-use run continued learning with policy lag 64, while a Qwen3-30B-A3B mixture-of-experts run raised four-benchmark macro pass@1 from 31.29% to 71.55% over 3,000 updates.

The comparison with standard kernels is the sharper result. The authors report that standard-kernel asynchronous importance sampling produced an 83.33× rise in rollout-to-learner KL divergence and a peak-to-median importance-weight deviation ratio of 442.54. With aligned kernels, KL stayed flat and that ratio fell to 1.50.

Why it matters for vLLM users

The work extends an earlier vLLM effort to make rollout and training agree exactly. The new report applies that consistency to asynchronous training and validates the path across reasoning, Python tool use and visual computer-use workloads.

It also broadens the hardware and model coverage. The team reports zero-mismatch execution for DeepSeek-V4.1-Flash and day-zero support for Kimi K3.1, including LoRA training. It validated DeepSeek-V4-Flash and Kimi K3.1 paths on AMD MI355X accelerators as well as NVIDIA systems. The implementation materials, model-specific recipes and an agent-executable kernel-alignment skill are published as open source.

The caveat

Kernel alignment is not free. The report says aligned execution increased the mean end-to-end training-step time by 6.8% on an OSWorld workload compared with the standard-kernel baseline. For some AMD paths, the team still lists performance optimization as ongoing.

That trade is the point: accept a modest per-step cost to remove numerical disagreement, then recover more time by overlapping rollout and learning without destabilizing the run. The evidence is promising, but the flagship-model section currently reports alignment validation rather than long asynchronous training runs; those are explicitly listed as next work.

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.