On GDDR7/Blackwell (measured: RTX 5090, driver 615.78.08) the memory
V/F offset NVML APIs operate in a domain 2x the memory clock NVML
reports. Applying +3000 moved the under-load clock by only +1500 MHz;
the driver range -2000..+6000 maps to NvAPI's -1000..+3000.
- limits.py: multiply by _MEM_OFFSET_DOMAIN_FACTOR (2) on set, divide
on get/readback/range for the MEM domain only; GPC untouched.
API/CLI/profiles/UI now all speak the reported-clock domain
(what nvidia-smi shows), so a +3000 slider value reaches the
driver's full +6000 headroom (old UI half-used it).
- limits.py: call nvmlDeviceGet/SetClockOffsets via the raw function
pointer for the real driver return code - nvidia-ml-py wrappers
discard it and always report success, which would have masked
erroring drivers and skipped the deprecated-API fallbacks.
- PerformancePanel: fallback range -1000..+3000, remove stale
Math.min(max, 3000) cap that clamped the new max, add domain tooltip.
- Docs: document the domain conversion (API.md, Usage-Guide.md).
Add a GPU process table to the Performance tab showing which processes
use the selected GPU, with per-process VRAM, GPU utilization, CPU, host
memory, and command. Includes a kill endpoint (SIGTERM/SIGKILL, with
optional parent kill) behind a confirm dialog.
- nvcurve/hal/processes.py: NVML + /proc process enumeration
- server.py: GET /api/processes, POST /api/processes/kill (refuses to
signal init/kthreadd)
- frontend: ProcessList component, API client, types
- tests: test_processes.py
- docs: API reference for the new endpoints
- docs/API.md: full REST + WebSocket reference with auth usage
(cookie/Bearer login flow, curl examples), conventions, endpoint
tables, and WS protocol (WS routes are not in the OpenAPI schema)
- server.py: app-level description, openapi_tags grouping, and
tags/responses metadata on all REST routes documenting the error
codes each route raises; hide the SPA catch-all from the schema
- README: link the API reference in the docs index