From: Randy Dunlap <rdunlap@infradead.org>
To: mohamedalrshah <mohamed.a.alrshah@ieee.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, Mohamed Othman <mothman@upm.edu.my>,
Borhanuddin Ali <borhan@upm.edu.my>,
Zurina Hanapi <zurinamh@upm.edu.my>
Subject: Re: [PATCH] Adding-Agile-SD-TCP-module-and-modifying-Kconfig-and-makefile
Date: Tue, 15 Aug 2017 10:10:46 -0700 [thread overview]
Message-ID: <f4104741-a918-c102-ffaa-0221fadda82e@infradead.org> (raw)
In-Reply-To: <20170815130806.25168-1-mohamed.a.alrshah@ieee.org>
On 08/15/2017 06:08 AM, mohamedalrshah wrote:
> diff --git a/net/ipv4/Kconfig b/net/ipv4/Kconfig
> index 91a2557..474f72c 100644
> --- a/net/ipv4/Kconfig
> +++ b/net/ipv4/Kconfig
> @@ -677,6 +677,17 @@ config TCP_CONG_BBR
> bufferbloat, policers, or AQM schemes that do not provide a delay
> signal. It requires the fq ("Fair Queue") pacing packet scheduler.
>
> +config TCP_CONG_AGILESD
> + tristate "Agile-SD Congestion control"
> + default n
> + ---help---
> +
> + This is version 1.0 of Agile-SD TCP. It is a sender-side only.
It is a sender-side only <what>.
> + It contributes the Agility Factor (AF) to shorten the epoch time
> + and to make TCP independent from RTT. AF reduces the sensitivity
> + to packet losses, which in turn Agile-SD to achieve better throughput
in turn allows Agile-SD
> + over high-speed networks.
> +
Please drop the tab(s) and space(s) at the ends of lines.
> choice
> prompt "Default TCP congestion control"
> default DEFAULT_CUBIC
> @@ -713,6 +724,9 @@ choice
>
> config DEFAULT_BBR
> bool "BBR" if TCP_CONG_BBR=y
> +
> + config DEFAULT_AGILESD
Indent above with tab, not spaces.
> + bool "AGILESD" if TCP_CONG_AGILESD=y
>
> config DEFAULT_RENO
> bool "Reno"
> @@ -738,6 +752,7 @@ config DEFAULT_TCP_CONG
> default "dctcp" if DEFAULT_DCTCP
> default "cdg" if DEFAULT_CDG
> default "bbr" if DEFAULT_BBR
> + default "agilesd" if DEFAULT_AGILESD
Indent above with tab, not spaces.
> default "cubic"
>
> config TCP_MD5SIG
--
~Randy
next prev parent reply other threads:[~2017-08-15 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 13:08 mohamedalrshah
2017-08-15 13:51 ` Neal Cardwell
2017-08-15 16:41 ` Randy Dunlap
2017-08-15 17:36 ` David Miller
2017-08-15 17:50 ` Randy Dunlap
2017-08-15 14:01 ` Neal Cardwell
2017-08-15 17:10 ` Randy Dunlap [this message]
2017-08-16 23:36 ` kbuild test robot
2017-08-17 0:12 ` kbuild test robot
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=f4104741-a918-c102-ffaa-0221fadda82e@infradead.org \
--to=rdunlap@infradead.org \
--cc=borhan@upm.edu.my \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mohamed.a.alrshah@ieee.org \
--cc=mothman@upm.edu.my \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zurinamh@upm.edu.my \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®