From: Jeff Garzik <jeff@garzik.org>
To: Masakazu Mokuno <mokuno@sm.sony.co.jp>
Cc: Linas Vepstas <linas@austin.ibm.com>,
netdev@vger.kernel.org, cbe-oss-dev@ozlabs.org,
geoffrey.levand@am.sony.com,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Subject: Re: [PATCH 1/2] PS3: improve tx throughput for gelic driver
Date: Fri, 31 Aug 2007 06:57:03 -0400 [thread overview]
Message-ID: <46D7F3FF.5080503@garzik.org> (raw)
In-Reply-To: <20070829143537.C2D2.MOKUNO@sm.sony.co.jp>
Masakazu Mokuno wrote:
> Improve tx throughputs.
> netperf score gained approximately 20%
This is a useless patch description. It does not adequately summarize
the changes contained within the patch.
Please resubmit patch with a useful patch description
next parent reply other threads:[~2007-08-31 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070829143537.C2D2.MOKUNO@sm.sony.co.jp>
2007-08-31 10:57 ` Jeff Garzik [this message]
2007-08-31 11:52 ` [PATCH 1/2] PS3: improve tx throughput for gelic driver Masakazu Mokuno
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=46D7F3FF.5080503@garzik.org \
--to=jeff@garzik.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=cbe-oss-dev@ozlabs.org \
--cc=geoffrey.levand@am.sony.com \
--cc=linas@austin.ibm.com \
--cc=mokuno@sm.sony.co.jp \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).