From a0f031c69244456c67fc5d9f38ee34a5d4511f15 Mon Sep 17 00:00:00 2001 From: "Jason A. Donenfeld" Date: Wed, 3 Jul 2019 12:21:32 +0000 Subject: Do not use _RESOURCES but rather allocate our own copy Signed-off-by: Jason A. Donenfeld Fixes: 09dc932 ("Create copies of NBLs to complete them faster") --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index a572ed9..3a01a0d 100644 --- a/README.md +++ b/README.md @@ -119,6 +119,6 @@ After loading the driver and creating a network interface the typical way using ~ ~ ``` -Each packet segment should contain a layer 3 IPv4 or IPv6 packet. Up to 15728640 bytes may be read or written during each call to `ReadFile` or `WriteFile`. All calls to `ReadFile` must be called with the same virtual address, and all calls to `WriteFile` must be called with the same virtual address. These virtual addresses must reference pages that are readable and writable for the same length as passed to the first calls of `ReadFile` and `WriteFile`. +Each packet segment should contain a layer 3 IPv4 or IPv6 packet. Up to 15728640 bytes may be read or written during each call to `ReadFile` or `WriteFile`. All calls to `ReadFile` must be called with the same virtual address, for a given handle. This virtual address must reference pages that are writable for the same length as passed to the first call of `ReadFile`. It is advisable to use [overlapped I/O](https://docs.microsoft.com/en-us/windows/desktop/sync/synchronization-and-overlapped-input-and-output) for this. If using blocking I/O instead, it may be desirable to open separate handles for reading and writing. -- cgit v1.2.3-59-g8ed1b