From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH net-next-2.6 00/10] sfc changes for 2.6.37
Date: Fri, 10 Sep 2010 12:28:54 -0700 (PDT) [thread overview]
Message-ID: <20100910.122854.184831961.davem@davemloft.net> (raw)
In-Reply-To: <1284136817.2267.93.camel@achroite.uk.solarflarecom.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Fri, 10 Sep 2010 17:40:17 +0100
> One new feature - variable ring sizes - and a few bug fixes.
>
> Ben.
>
> Ben Hutchings (9):
> sfc: Use MCDI RX_BAD_FCS_PKTS count as MAC rx_bad count
> sfc: Accumulate RX_NODESC_DROP count in rx_dropped, not
> rx_over_errors
> sfc: Remove declarations of functions that no longer exist
> sfc: Fix failure paths in efx_probe_port()
> sfc: Allocate DMA and event rings using GFP_KERNEL
> sfc: Abstract channel and index lookup for RX queues
> sfc: Refactor channel and queue lookup and iteration
> sfc: Allocate each channel separately, along with its RX and TX
> queues
> sfc: Allow changing the DMA ring sizes dynamically via ethtool
>
> Steve Hodgson (1):
> sfc: Make the dmaq size a run-time setting (rather than compile-time)
All applied, thanks Ben.
It could be argued that rx_over_errors is meant to count internal chip
FIFO overflows during receive, which occur when DMA cannot meet demand
for long periods of time. Indicating that FIFO settings need to be
increased or PCI settings adjusted.
Anyways, just my view.
next prev parent reply other threads:[~2010-09-10 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 16:40 [PATCH net-next-2.6 00/10] sfc changes for 2.6.37 Ben Hutchings
2010-09-10 16:41 ` [PATCH net-next-2.6 01/10] sfc: Use MCDI RX_BAD_FCS_PKTS count as MAC rx_bad count Ben Hutchings
2010-09-10 16:41 ` [PATCH net-next-2.6 02/10] sfc: Accumulate RX_NODESC_DROP count in rx_dropped, not rx_over_errors Ben Hutchings
2010-09-10 16:41 ` [PATCH net-next-2.6 03/10] sfc: Remove declarations of functions that no longer exist Ben Hutchings
2010-09-10 16:41 ` [PATCH net-next-2.6 04/10] sfc: Fix failure paths in efx_probe_port() Ben Hutchings
2010-09-10 16:41 ` [PATCH net-next-2.6 05/10] sfc: Allocate DMA and event rings using GFP_KERNEL Ben Hutchings
2010-09-10 16:41 ` [PATCH net-next-2.6 06/10] sfc: Abstract channel and index lookup for RX queues Ben Hutchings
2010-09-10 16:41 ` [PATCH net-next-2.6 07/10] sfc: Refactor channel and queue lookup and iteration Ben Hutchings
2010-09-10 16:41 ` [PATCH net-next-2.6 08/10] sfc: Allocate each channel separately, along with its RX and TX queues Ben Hutchings
2010-09-10 16:42 ` [PATCH net-next-2.6 09/10] sfc: Make the dmaq size a run-time setting (rather than compile-time) Ben Hutchings
2010-09-10 16:42 ` [PATCH net-next-2.6 10/10] sfc: Allow changing the DMA ring sizes dynamically via ethtool Ben Hutchings
2010-09-10 19:28 ` David Miller [this message]
2010-09-10 19:59 ` [PATCH net-next-2.6 00/10] sfc changes for 2.6.37 Ben Hutchings
2010-09-13 5:29 ` David Miller
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=20100910.122854.184831961.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=linux-net-drivers@solarflare.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).