All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 25 Aug 2011 13:46:58 +0900	[thread overview]
Message-ID: <4E55D3C2.40308@ctc-g.co.jp> (raw)
In-Reply-To: <20110822.113544.28950168095176936.davem@davemloft.net>

Currently, once the transmission buffer becomes full, it is not
possible to write again unless there is one third of free space
in the transmission buffer.

Our modification request is not intending to change the behavior
of the OS itself, but making the value "one third" to be
configurable, not fixed.

Thus it would be still possible to set the value to 1/3.

So, could you please tell us why it is not acceptable to make
it configurable, and what is the persistence with the value of
1/3?



  reply	other threads:[~2011-08-25  4:47 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   ` [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 14:21           ` Hagen Paul Pfeifer
2011-08-22 18:35         ` David Miller
2011-08-25  4:46           ` Jun.Kondo [this message]
2011-08-25  5:00             ` [omega-g1:11110] " 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=4E55D3C2.40308@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.