netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Richter <adam_richter2004@yahoo.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: davem@davemloft.net, netdev@vger.kernel.org, berkley@cs.wustl.edu
Subject: Re: 2.6.29 forcedeth hang W/O NAPI enabled
Date: Thu, 26 Mar 2009 16:29:24 -0700 (PDT)	[thread overview]
Message-ID: <56812.58166.qm@web57708.mail.re3.yahoo.com> (raw)
In-Reply-To: <20090326065825.GA15730@gondor.apana.org.au>


On Wed, 3/25/09, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> Thanks for testing! Since you also have a forcedeth card,
> could
> you try rebuilding your kernel with FORCEDETH_NAPI enabled
> and
> see if that is stable?

It works so far, doing "ping -f" for more than five minutes while I
browse the web, but bear in mind that I was not able to reproduce the
problem earlier with FORCEDETH_NAPI on demand.  I only saw an ethernet lock up with NAPI enabled once (with the original 2.6.29 code).  I
will let you know if the lockup occurs with your code. 

Just to be clear which version I am now testing, I have attached a
copy of process_backlog() from my net/core/dev.c.

Adam



static int process_backlog(struct napi_struct *napi, int quota)
{
	int work = 0;
	struct softnet_data *queue = &__get_cpu_var(softnet_data);
	unsigned long start_time = jiffies;

	napi->weight = weight_p;
	do {
		struct sk_buff *skb;

		local_irq_disable();
		skb = __skb_dequeue(&queue->input_pkt_queue);
		if (!skb) {
			list_del(&napi->poll_list);
			clear_bit(NAPI_STATE_SCHED, &napi->state);
			local_irq_enable();
			break;
		}
		local_irq_enable();

		napi_gro_receive(napi, skb);
	} while (++work < quota && jiffies == start_time);

	napi_gro_flush(napi);

	return work;
}



      

  reply	other threads:[~2009-03-26 23:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 23:24 2.6.29 forcedeth hang W/O NAPI enabled Adam Richter
2009-03-26  0:05 ` David Miller
2009-03-26  1:20   ` Adam Richter
2009-03-26  3:14     ` David Miller
2009-03-26  3:36     ` Herbert Xu
2009-03-26  5:24       ` Adam Richter
2009-03-26  6:58         ` Herbert Xu
2009-03-26 23:29           ` Adam Richter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-26  0:06 Adam Richter
2009-03-26  0:08 ` David Miller
2009-03-24 15:28 Mr. Berkley Shands

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=56812.58166.qm@web57708.mail.re3.yahoo.com \
    --to=adam_richter2004@yahoo.com \
    --cc=berkley@cs.wustl.edu \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --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).