From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next PATCH 00/11] ixgbe: Add support for writable pages and build_skb
Date: Fri, 06 Jan 2017 17:12:04 -0800 [thread overview]
Message-ID: <1483751524.25700.86.camel@intel.com> (raw)
In-Reply-To: <20170106.164116.1871412141301427533.davem@davemloft.net>
On Fri, 2017-01-06 at 16:41 -0500, David Miller wrote:
> From: Alexander Duyck <alexander.duyck@gmail.com>
> Date: Fri, 06 Jan 2017 08:06:16 -0800
>
> > The testing matrix for all of these patches is going to be pretty
> > extensive.? Basically we want to test these patches on as many
> > platforms
> > and architectures as possible with as many features being toggled as
> > possible including RSC, FCoE, SR-IOV, and Jumbo Frames all while
> > receiving
> > traffic.
>
> Overall looks very nice to me.
>
> I am assuming that I will get a formal submission once the necessary
> amount of testing is performed.
Yes, your assumption is correct. :-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20170106/1c31d7a5/attachment.asc>
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>, alexander.duyck@gmail.com
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [next PATCH 00/11] ixgbe: Add support for writable pages and build_skb
Date: Fri, 06 Jan 2017 17:12:04 -0800 [thread overview]
Message-ID: <1483751524.25700.86.camel@intel.com> (raw)
In-Reply-To: <20170106.164116.1871412141301427533.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
On Fri, 2017-01-06 at 16:41 -0500, David Miller wrote:
> From: Alexander Duyck <alexander.duyck@gmail.com>
> Date: Fri, 06 Jan 2017 08:06:16 -0800
>
> > The testing matrix for all of these patches is going to be pretty
> > extensive. Basically we want to test these patches on as many
> > platforms
> > and architectures as possible with as many features being toggled as
> > possible including RSC, FCoE, SR-IOV, and Jumbo Frames all while
> > receiving
> > traffic.
>
> Overall looks very nice to me.
>
> I am assuming that I will get a formal submission once the necessary
> amount of testing is performed.
Yes, your assumption is correct. :-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-01-07 1:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 16:06 [Intel-wired-lan] [next PATCH 00/11] ixgbe: Add support for writable pages and build_skb Alexander Duyck
2017-01-06 16:06 ` Alexander Duyck
2017-01-06 16:06 ` [Intel-wired-lan] [next PATCH 01/11] ixgbe: Add function for checking to see if we can reuse page Alexander Duyck
2017-01-06 16:06 ` Alexander Duyck
2017-01-06 16:06 ` [Intel-wired-lan] [next PATCH 02/11] ixgbe: Only DMA sync frame length Alexander Duyck
2017-01-06 16:06 ` Alexander Duyck
2017-01-06 16:06 ` [Intel-wired-lan] [next PATCH 03/11] ixgbe: Update driver to make use of DMA attributes in Rx path Alexander Duyck
2017-01-06 16:06 ` Alexander Duyck
2017-01-06 16:06 ` [Intel-wired-lan] [next PATCH 04/11] ixgbe: Update code to better handle incrementing page count Alexander Duyck
2017-01-06 16:06 ` Alexander Duyck
2017-01-07 13:06 ` [Intel-wired-lan] " kbuild test robot
2017-01-07 13:06 ` kbuild test robot
2017-01-06 16:07 ` [Intel-wired-lan] [next PATCH 05/11] ixgbe: Make use of order 1 pages and 3K buffers independent of FCoE Alexander Duyck
2017-01-06 16:07 ` Alexander Duyck
2017-01-06 16:07 ` [Intel-wired-lan] [next PATCH 06/11] ixgbe: Use length to determine if descriptor is done Alexander Duyck
2017-01-06 16:07 ` Alexander Duyck
2017-01-06 16:07 ` [Intel-wired-lan] [next PATCH 07/11] ixgbe: Break out Rx buffer page management Alexander Duyck
2017-01-06 16:07 ` Alexander Duyck
2017-01-06 16:07 ` [Intel-wired-lan] [next PATCH 08/11] ixgbe: Add support for padding packet Alexander Duyck
2017-01-06 16:07 ` Alexander Duyck
2017-01-06 16:07 ` [Intel-wired-lan] [next PATCH 09/11] ixgbe: Add private flag to control buffer mode Alexander Duyck
2017-01-06 16:07 ` Alexander Duyck
2017-01-06 16:07 ` [Intel-wired-lan] [next PATCH 10/11] ixgbe: Add support for build_skb Alexander Duyck
2017-01-06 16:07 ` Alexander Duyck
2017-01-06 16:07 ` [Intel-wired-lan] [next PATCH 11/11] ixgbe: Don't bother clearing buffer memory for descriptor rings Alexander Duyck
2017-01-06 16:07 ` Alexander Duyck
2017-01-06 21:41 ` [Intel-wired-lan] [next PATCH 00/11] ixgbe: Add support for writable pages and build_skb David Miller
2017-01-06 21:41 ` David Miller
2017-01-07 1:12 ` Jeff Kirsher [this message]
2017-01-07 1:12 ` Jeff Kirsher
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=1483751524.25700.86.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.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 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.