netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH 1/5] sfc: Pad packets to 33 bytes to prevent TX packet parser lockup
Date: Sat, 21 Mar 2009 19:09:42 -0700 (PDT)	[thread overview]
Message-ID: <20090321.190942.86384309.davem@davemloft.net> (raw)
In-Reply-To: <1237591540.3217.6.camel@achroite>

From: Ben Hutchings <bhutchings@solarflare.com>
Date: Fri, 20 Mar 2009 23:25:39 +0000

> The packet parser used in the TX data path for locating checksum
> fields can lose synchronisation with the TX queue manager when
> handling packets that look like IPv4 but are too short (17-32 bytes).
> Work around this by padding to 33 bytes.
> 
> Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>

Applied.

      parent reply	other threads:[~2009-03-22  2:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-20 23:25 [PATCH 1/5] sfc: Pad packets to 33 bytes to prevent TX packet parser lockup Ben Hutchings
2009-03-20 23:26 ` [PATCH 2/5] sfc: Work around unreliable legacy interrupt status Ben Hutchings
2009-03-22  2:09   ` David Miller
2009-03-20 23:26 ` [PATCH 3/5] sfc: Remove unused private PCI register definitions Ben Hutchings
2009-03-22  2:09   ` David Miller
2009-03-20 23:27 ` [PATCH 4/5] sfc: Optimise falcon_writel_page_locked() for page > 0 Ben Hutchings
2009-03-22  2:10   ` David Miller
2009-03-20 23:30 ` [PATCH 5/5] sfc: Implement adaptive IRQ moderation Ben Hutchings
2009-03-22  2:10   ` David Miller
2009-03-22  2:09 ` David Miller [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=20090321.190942.86384309.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).