From: Jeff Garzik <jeff@garzik.org>
To: Brice Goglin <brice@myri.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] myri10ge: write as 2 32-byte blocks in myri10ge_submit_8rx
Date: Mon, 04 Dec 2006 18:36:25 -0500 [thread overview]
Message-ID: <4574B0F9.9070409@garzik.org> (raw)
In-Reply-To: <4573F97B.90707@myri.com>
Brice Goglin wrote:
> In the myri10ge_submit_8rx() routine, write the 64 byte request block as
> 2 32-byte blocks so that it is handled by the hardware pio write handler
> if write-combining is enabled.
>
> Signed-off-by: Brice Goglin <brice@myri.com>
> ---
> drivers/net/myri10ge/myri10ge.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
ACK, can you resend due to patch collision in #upstream?
Jeff
next prev parent reply other threads:[~2006-12-04 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 10:31 [PATCH 0/1] small myri10ge fix for 2.6.20 Brice Goglin
2006-12-04 10:33 ` [PATCH 1/1] myri10ge: write as 2 32-byte blocks in myri10ge_submit_8rx Brice Goglin
2006-12-04 23:36 ` Jeff Garzik [this message]
2006-12-05 15:28 ` Brice Goglin
2006-12-05 16:26 ` Brice Goglin
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=4574B0F9.9070409@garzik.org \
--to=jeff@garzik.org \
--cc=brice@myri.com \
--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).