|author||Simon Rozman <firstname.lastname@example.org>||2019-06-05 11:52:15 +0200|
|committer||Jason A. Donenfeld <Jason@zx2c4.com>||2019-06-07 12:28:07 +0200|
|parent||Check number of packets in exchange buffer for overflow (diff)|
README: 256 packets per exchange buffer limitation is obsolete
Signed-off-by: Simon Rozman <email@example.com>
Diffstat (limited to 'README.md')
1 files changed, 1 insertions, 1 deletions
@@ -117,6 +117,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 256 packets may be read or written during each call to `ReadFile` or `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`.
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.