public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: "Jun.Kondo" <jun.kondo@ctc-g.co.jp>
Cc: linux-kernel@vger.kernel.org,
	"omega-g1@ctc-g.co.jp" <omega-g1@ctc-g.co.jp>,
	notsuki@redhat.com, "Kozaki, Motokazu" <motokazu.kozaki@hp.com>,
	Hajime Taira <htaira@redhat.com>,
	netdev@vger.kernel.org
Subject: Re: Request for Redhat
Date: Fri, 12 Aug 2011 09:18:05 -0700	[thread overview]
Message-ID: <20110812161805.GI9766@sequoia.sous-sol.org> (raw)
In-Reply-To: <4E450C8F.4030009@ctc-g.co.jp>

Hi Jun,

* Jun.Kondo (jun.kondo@ctc-g.co.jp) wrote:
> CTC had the following demand;
> 
> 1. to ensure high throughput from the beginning of
> tcp connection at normal times by acquiring large
> default transmission buffer value
> 
> 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

Make sure you include network developers (netdev@vger.kernel.org Cc'd)
on networking related patches.

You'll find some helpful information regarding the email format for
submitting patches here:
  http://www.kernel.org/doc/Documentation/SubmittingPatches

Improving your Subject: and fixing the patch level for your diff come
to mind immediately.

> --- sock.h 2011-04-14 14:58:03.000000000 +0900
> +++ sock.h.mod 2011-04-21 15:30:07.000000000 +0900
> @@ -434,9 +434,12 @@
> /*
> * Compute minimal free write space needed to queue new packets.
> */
> +
> +extern int sysctl_tcp_lowat;
> +
> static inline int sk_stream_min_wspace(struct sock *sk)
> {
> - return sk->sk_wmem_queued / 2;
> + return sk->sk_wmem_queued >> sysctl_tcp_lowat;
> }

Also, this patch appears to be against an old tree (I assume the RHEL
5 tree).  To be considered upstream, you need to generate a diff against
the upstream tree.  And considering all that's changed since 2.6.18, it
would be useful to verify you still have the issue in a current upstream
Linux tree.

Alternatively, you may consider using Red Hat's Bugzilla to contact RH
engineers for help and guidance.

Good luck.

thanks,
-chris

      reply	other threads:[~2011-08-12 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 11:20 Request for Redhat Jun.Kondo
2011-08-12 16:18 ` Chris Wright [this message]

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=20110812161805.GI9766@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=htaira@redhat.com \
    --cc=jun.kondo@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 \
    /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