linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: David Schleef <ds@schleef.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: bugfix patch to arch/ppc/8260_io/fcc_enet.c
Date: Sun, 08 Apr 2001 03:15:29 -0400	[thread overview]
Message-ID: <3AD01011.A8FAB831@mvista.com> (raw)
In-Reply-To: 20010406071644.A2517@stm.lbl.gov


David Schleef wrote:
>
> The attached patch fixes a bug with 8260 fcc_enet driver that
> is related to when the TX buffer becomes full.

Well, you need to prove to me you don't have a wrap-around
problem.  The line:
	if(cep->skb_cur - cep->skb_dirty >= TX_RING_SIZE){

is in big trouble, and I suspect you changed these from shorts
to ints because it didn't work right.  I suspect all you did
was postpone the problem until you hit 4G of packets instead of 64K.


> ..... Currently,
> the driver relies on the BD_ENET_TX_READY for determining if
> a ring slot is available for a tx buffer.  This is not a
> valid criterion, because the interrupt handler may not have
> cleared the slot from a previous tx buffer.

I beg to differ.  It is a valid criterion because the interrupt
handler isn't responsible for clearing the flag.  The transmit
function sets it, and the CPM will clear it when it is done sending
the buffer.

You are going to have big problems if you are writing into buffers
that have this flag set.

> ..... This bug is easy
> to generate by writing files over NFS with large wsize.

Then, there is some other bug that needs to be found and fixed.....



	-- Dan

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-04-08  7:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-06 14:16 bugfix patch to arch/ppc/8260_io/fcc_enet.c David Schleef
2001-04-08  7:15 ` Dan Malek [this message]
2001-04-08 22:28   ` David Schleef
2001-04-09 17:57     ` Dan Malek
2001-04-09 20:10     ` Dan Malek

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=3AD01011.A8FAB831@mvista.com \
    --to=dan@mvista.com \
    --cc=ds@schleef.org \
    --cc=linuxppc-dev@lists.linuxppc.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).