diff options
| author | Ramon Fried <rfried.dev@gmail.com> | 2020-07-18 23:31:46 +0300 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2020-08-04 23:30:02 -0400 |
| commit | cc6b87ecaa96325577a8fafabc0d5972b816bc6c (patch) | |
| tree | 627f2154947c30d57ecb1357c92935939419d367 /net/Kconfig | |
| parent | 5cc7df7ebaccc0d02e3322a35b2dcb47951bc9ae (diff) | |
| download | u-boot-cc6b87ecaa96325577a8fafabc0d5972b816bc6c.zip u-boot-cc6b87ecaa96325577a8fafabc0d5972b816bc6c.tar.gz u-boot-cc6b87ecaa96325577a8fafabc0d5972b816bc6c.tar.bz2 | |
net: tftp: Add client support for RFC 7440
Add support for RFC 7440: "TFTP Windowsize Option".
This optional feature allows the client and server
to negotiate a window size of consecutive blocks to send as an
alternative for replacing the single-block lockstep schema.
windowsize can be defined statically during compilation by
setting CONFIG_TFTP_WINDOWSIZE, or defined in runtime by
setting an environment variable: "tftpwindowsize"
If not defined, the windowsize is set to 1, meaning that it
behaves as it was never defined.
Choosing the appropriate windowsize depends on the specific
network topology, underlying NIC.
You should test various windowsize scenarios and see which
best work for you.
Setting a windowsize too big can actually decreases performance.
Signed-off-by: Ramon Fried <rfried.dev@gmail.com>
Reviewed-by: Marek Vasut <marex@denx.de>
Diffstat (limited to 'net/Kconfig')
| -rw-r--r-- | net/Kconfig | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/net/Kconfig b/net/Kconfig index 6c47b7d..6874b55 100644 --- a/net/Kconfig +++ b/net/Kconfig @@ -59,4 +59,13 @@ config TFTP_BLOCKSIZE almost-MTU block sizes. You can also activate CONFIG_IP_DEFRAG to set a larger block. +config TFTP_WINDOWSIZE + int "TFTP window size" + default 1 + help + Default TFTP window size. + RFC7440 defines an optional window size of transmits, + before an ack response is required. + The default TFTP implementation implies a window size of 1. + endif # if NET |