From: emersonbusson <emersonbusson@gmail.com>
To: linux-block@vger.kernel.org
Cc: axboe@kernel.dk, linux-kernel@vger.kernel.org,
emersonbusson <emersonbusson@gmail.com>
Subject: [RFC PATCH v2 0/2] drivers/block: add RamShared hardware-accelerated VRAM block driver
Date: Fri, 4 Sep 2026 04:38:13 -0300 [thread overview]
Message-ID: <6a9a756e.4675fc7e.263ae0.66e6@mx.google.com> (raw)
This patch series introduces the RamShared hardware-accelerated
block driver (drivers/block/ramshared).
RamShared maps discrete GPU video memory (VRAM) apertures over direct
PCIe DMA to provide an ultra-low latency, non-rotational block device
with a synchronous .rw_page swapout path.
Key Design Highlights:
1. blk-mq multi-queue parallel request processing with atomic gendisk
allocation.
2. Synchronous .rw_page fast-path in block_device_operations for
zero-allocation swapout under direct memory reclaim pressure.
3. PCIe AER error handling with pci_error_handlers to contain link resets.
4. Comprehensive multi-kernel compatibility across 5.15 LTS through 6.18+.
v1 -> v2 changes:
- drivers/block/ramshared/queue.c: use check_shl_overflow() to prevent
64-bit integer overflow when shifting sector to byte offsets.
- drivers/block/ramshared/queue.c: enforce PCIe BAR0 boundary validation
before memory-mapped I/O.
- drivers/block/ramshared/main.c: ensure pci_clear_master() is called
during linear error unwinding in probe failure paths and device teardown.
- drivers/block/ramshared/main.c: clamp queue_depth module parameter
within [1..4096].
- drivers/block/ramshared/ramshared.h: wrap function declarations to
conform to 80-column kernel coding style.
Testing & Quality Gates:
- checkpatch.pl --strict: 0 errors, 0 checks.
- sparse semantic address-space analysis: PASS (__iomem verified).
- Multi-tier saturation benchmark: 9,160 MB swap holding 40 continuous
cycles over 30 seconds with 0.00 ms access latency under WSL2/Hyper-V
(EVD-0040).
- Memory stress battery: 9.09 GB/s PCIe reclaim throughput with
0.0% PSI stalls.
Signed-off-by: emersonbusson <emersonbusson@gmail.com>
reply other threads:[~2026-09-04 7:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a9a756e.4675fc7e.263ae0.66e6@mx.google.com \
--to=emersonbusson@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.