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:10937] Re: [PATCH] net: configurable sysctl parameter "net.core.tcp_lowat" for sk_stream_min_wspace()
Date: Fri, 19 Aug 2011 18:28:45 +0900 [thread overview]
Message-ID: <4E4E2CCD.6050809@ctc-g.co.jp> (raw)
In-Reply-To: <20110814.224714.2061635645365376268.davem@davemloft.net>
You suggested to use non-blocking writes, but we think
we have to rewrite the Apache code if doing so.
That is, we have to make a modification to Apache that
depends on the architecture.
By using this patch, it can be handled by changing the
configuration a little bit on the kernel side for such
applications that it is difficult to do so on application
side.
(2011/08/15 14:47), David Miller wrote:
> From: "Jun.Kondo"<jun.kondo@ctc-g.co.jp>
> Date: Mon, 15 Aug 2011 14:38:11 +0900
>
>> 2. to limit the block time of the write in order to
>> prevent the timeout of upper layer applications
>> even when the connection has low throughput, such
>> as low rate streaming
> Use non-blocking writes if you want this behavior.
>
next prev parent reply other threads:[~2011-08-19 9:29 UTC|newest]
Thread overview: 12+ 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 ` Jun.Kondo [this message]
2011-08-19 9:43 ` [omega-g1:10937] " David Miller
2011-08-22 0:33 ` [omega-g1:11072] " Jun.Kondo
2011-08-22 14:21 ` Hagen Paul Pfeifer
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
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=4E4E2CCD.6050809@ctc-g.co.jp \
--to=jun.kondo@ctc-g.co.jp \
--cc=davem@davemloft.net \
--cc=htaira@redhat.com \
--cc=ken.sugawara@ctc-g.co.jp \
--cc=kotaro.sakai@ctc-g.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=motokazu.kozaki@hp.com \
--cc=netdev@vger.kernel.org \
--cc=notsuki@redhat.com \
--cc=omega-g1@ctc-g.co.jp \
--cc=tomohiko.takahashi@ctc-g.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.