From: "Jun.Kondo" <jun.kondo@ctc-g•co.jp>
To: David Miller <davem@davemloft•net>
Cc: linux-kernel@vger•kernel.org, omega-g1@ctc-g•co.jp,
notsuki@redhat•com, motokazu.kozaki@hp•com, htaira@redhat•com,
netdev@vger•kernel.org, tomohiko.takahashi@ctc-g•co.jp,
kotaro.sakai@ctc-g•co.jp, ken.sugawara@ctc-g•co.jp
Subject: Re: [omega-g1:11110] Re: [PATCH] net: configurable sysctl parameter "net.core.tcp_lowat" for sk_stream_min_wspace()
Date: Fri, 09 Sep 2011 10:33:58 +0900 [thread overview]
Message-ID: <4E696D06.3000003@ctc-g.co.jp> (raw)
In-Reply-To: <20110824.220016.781758659534965980.davem@davemloft.net>
The client of this system is cellular phone, and the
status of the communication line with a client varies
widely according to its place or congestion situation.
In terms of the line speed, it can be around 9Mbps
when it is fast, but 8kbps when it is slow.
Requirement from customer is to provide stable service
in both situation.
- In normal situation, acquire large default transmission
buffer value, and ensure high throughput from the
beginning of tcp connection
- On the other hand, even when the connection has low
throughput, such as low rate streaming, transmit data
without timeout
However, when the throughput is low, it takes much time
for the transmission buffer to be freed, and timeout
will occur during that period.
Of course, the connection will not be disconnected when
the timeout of application is extended, but end user
would not wait patiently as long as 1 minute.
Therefore, we do not want to extend the timeout value.
By making the threshold, which makes write possible after
the buffer is blocked once, configurable, and set it to a
small value, it will be possible to return data to client
without making timeout occur.
So, we think the issue can be solved with this
modification.
next prev parent reply other threads:[~2011-09-09 1:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 5:38 [PATCH] net: configurable sysctl parameter "net.core.tcp_lowat" for sk_stream_min_wspace() Jun.Kondo
2011-08-15 5:47 ` David Miller
2011-08-19 9:28 ` [omega-g1:10937] " Jun.Kondo
2011-08-19 9:43 ` David Miller
2011-08-22 0:33 ` [omega-g1:11072] " Jun.Kondo
2011-08-22 14:21 ` Hagen Paul Pfeifer
2011-08-22 18:35 ` David Miller
2011-08-25 4:46 ` [omega-g1:11110] " Jun.Kondo
2011-08-25 5:00 ` David Miller
2011-09-09 1:33 ` Jun.Kondo [this message]
2011-09-09 2:17 ` David Miller
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=4E696D06.3000003@ctc-g.co.jp \
--to=jun.kondo@ctc-g$(echo .)co.jp \
--cc=davem@davemloft$(echo .)net \
--cc=htaira@redhat$(echo .)com \
--cc=ken.sugawara@ctc-g$(echo .)co.jp \
--cc=kotaro.sakai@ctc-g$(echo .)co.jp \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=motokazu.kozaki@hp$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=notsuki@redhat$(echo .)com \
--cc=omega-g1@ctc-g$(echo .)co.jp \
--cc=tomohiko.takahashi@ctc-g$(echo .)co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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