mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Cc: Manfred Spraul <manfred@colorfullife.com>,
	Ingo Molnar <mingo@elte.hu>, Ayaz Abdulla <aabdulla@nvidia.com>
Subject: [PATCH 0/6] forcedeth interrupt and task overhaul, v2
Date: Wed, 17 Oct 2007 01:52:51 -0400	[thread overview]
Message-ID: <20071017055251.GA19972@havoc.gtf.org> (raw)


These six changes can be found in the 'fe' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git

      [netdrvr] forcedeth: internal simplifications; changelog removal
      [netdrvr] forcedeth: timer overhaul
      [netdrvr] forcedeth: eliminate some duplicate irq handling code
      [netdrvr] forcedeth: unconditionally enable NAPI
      [netdrvr] forcedeth: use NAPI for TX completion
      [netdrvr] interrupt handling overhaul


I rewrote the previous forcedeth patchset, even though the direction and
methods are quite similar to the last patchset.

This hammers out bugs, problems, inconsistencies, mainly with interrupt
handling and locking.  This moves the driver towards removing the
disable_irq() usage, but does not actually take that step (yet).

A few changes just went upstream, too:

Ingo Molnar (1):
      forcedeth: fix NAPI rx poll function
Jeff Garzik (2):
      [netdrvr] forcedeth: improved probe info; dev_printk() cleanups
      [netdrvr] forcedeth: remove in-driver copy of net_device_stats

This patchset is diff'd against the latest linux-2.6.git as of an hour
ago or so.  It applies on top of the three changes listed immediately
above this paragraph.

At this point, it has been tested on

	nVidia Corporation CK804 Ethernet Controller (rev a3)

but I'm definitely interested in other testing, particularly performance
numbers (wire speed? or below?), CPU usage and memory usage info.  Most
particularly CPU usage info.  And maybe interrupt count with/without
this patchset, too.

If you send feedback, 'dmesg' and 'lspci' output is helpful.  The
current forcedeth driver in upstream (0.61) prints out useful diagnostic
information about your chip at bootup.



             reply	other threads:[~2007-10-17  5:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17  5:52 Jeff Garzik [this message]
2007-10-17  5:53 ` [PATCH 1/6] forcedeth: internal simplifications; changelog removal Jeff Garzik
2007-10-17  5:53 ` [PATCH 2/6] forcedeth: timer overhaul Jeff Garzik
2007-10-17  5:54 ` [PATCH 3/6] forcedeth: eliminate some duplicate irq handling code Jeff Garzik
2007-10-17  5:54 ` [PATCH 4/6] forcedeth: unconditionally enable NAPI Jeff Garzik
2007-10-17  5:54 ` [PATCH 5/6] forcedeth: use NAPI for TX completion Jeff Garzik
2007-10-17  5:55 ` [PATCH 6/6] [netdrvr] interrupt handling overhaul Jeff Garzik
2007-10-17  5:59 ` [PATCH 0/6] forcedeth interrupt and task overhaul, v2 Jeff Garzik

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=20071017055251.GA19972@havoc.gtf.org \
    --to=jeff@garzik.org \
    --cc=aabdulla@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=mingo@elte.hu \
    --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

all inboxes | Powered by JetHome®