All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, davem@davemloft.net, nhorman@tuxdriver.com
Subject: [net-next PATCH 0/2] ixgbe: macvlan fixes
Date: Fri, 08 Nov 2013 00:50:07 -0800	[thread overview]
Message-ID: <20131108084654.6935.36501.stgit@nitbit.x32> (raw)

Two additional fixes for ixgbe l2 forwarding acceleration. One
was reported by kbuild build bot and the second after hardening
my test scripts.

Typically I would send ixgbe fixes through JeffK's tree but I
know a few people who are looking at the feature in their setup's 
so wanted to be sure the patches were visible.

For reference the ixgbe accelerated macvlan patch is here:

commit 2a47fa45d4dfbc54659d28de311a1f764b296a3c
Author: John Fastabend <john.r.fastabend@intel.com>
Date:   Wed Nov 6 09:54:52 2013 -0800

    ixgbe: enable l2 forwarding acceleration for macvlans

Thanks,
John

---

John Fastabend (2):
      ixgbe: fix build err, num_rx_queues is only available with CONFIG_RPS
      ixgbe: deleting dfwd stations out of order can cause null ptr deref


 drivers/net/ethernet/intel/ixgbe/ixgbe_main.c |   24 ++++++++++++++++--------
 1 file changed, 16 insertions(+), 8 deletions(-)

-- 
Signature

             reply	other threads:[~2013-11-08  8:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08  8:50 John Fastabend [this message]
2013-11-08  8:50 ` [net-next PATCH 1/2] ixgbe: fix build err, num_rx_queues is only available with CONFIG_RPS John Fastabend
2013-11-08 12:29   ` Neil Horman
2013-11-08 12:35   ` Jeff Kirsher
2013-11-08  8:51 ` [net-next PATCH 2/2] ixgbe: deleting dfwd stations out of order can cause null ptr deref John Fastabend
2013-11-08 12:31   ` Neil Horman
2013-11-08 12:36   ` Jeff Kirsher
2013-11-08 12:39 ` [net-next PATCH 0/2] ixgbe: macvlan fixes Jeff Kirsher
2013-11-08 20:21 ` David Miller
2013-11-08 20:40   ` kernel network panic stack traces on ubuntu 12.04 Templin, Fred L

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=20131108084654.6935.36501.stgit@nitbit.x32 \
    --to=john.fastabend@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.