From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <tj@home-tj.org>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCHES] via-velocity fixes
Date: Mon, 13 Sep 2004 02:03:28 -0400 [thread overview]
Message-ID: <41453830.9060708@pobox.com> (raw)
In-Reply-To: <20040913050255.GA32549@home-tj.org>
Tejun Heo wrote:
> Hello, I've encountered some problems (packet loss, duplicate
> truncated packets, hang) w/ recent rd ring related updates to
> via-veolcity. I'm attaching 8 patches to fix the problem and some
> other bugs. I'm attaching the following 8 patches. Detailed
> description is at the head of each patch file.
>
> 00velocity_nics.patch : velocity_nics management fix
> 01velocity_xmit_lock.patch : unused xmit_lock removed
> 02velocity_give_rx_desc.patch : give_rx_desc removed
> 03velocity_rd_ring.patch : rd ring fix (it was the offending bug)
> 04velocity_init.patch : init related bug fix
> 05velocity_cpu_to_le32.patch : removes cpu_to_le32(OWNED_BY_NIC)
> 06velocity_init_td_ring.patch : init_td_ring index calculation fix
> 07velocity_comment.patch : comment fixes
I'm reviewing these now, thanks.
Jeff
prev parent reply other threads:[~2004-09-13 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 5:02 [PATCHES] via-velocity fixes Tejun Heo
2004-09-13 6:03 ` Jeff Garzik [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=41453830.9060708@pobox.com \
--to=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=tj@home-tj.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).