From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next PATCH 9/9] igb: Revert "igb: Revert support for build_skb in igb"
Date: Fri, 06 Jan 2017 08:39:57 -0800 [thread overview]
Message-ID: <1483720797.25700.60.camel@intel.com> (raw)
In-Reply-To: <20170106161131.2030.4342.stgit@localhost.localdomain>
On Fri, 2017-01-06 at 08:11 -0800, Alexander Duyck wrote:
> From: Alexander Duyck <alexander.h.duyck@intel.com>
>
> This reverts commit f9d40f6a9921 ("igb: Revert support for build_skb in
> igb") and adds a few changes to update it to work with the latest version
> of igb. We are now able to revert the removal of this due to the fact
> that with the recent changes to the page count and the use of
> DMA_ATTR_SKIP_CPU_SYNC we can make the pages writable so we should not be
> invalidating the additional data added when we call build_skb.
>
> Signed-off-by: Alexander Duyck <alexander.h.duyck@intel.com>
> ---
> ?drivers/net/ethernet/intel/igb/igb_main.c |?? 47
> +++++++++++++++++++++++++++++
> ?1 file changed, 47 insertions(+)
Weird, this patch is not showing up in patchworks. I will get this patch
added as well to my tree and work on getting it to show up in patchworks.
-------------- 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/a0e96a3b/attachment.asc>
next prev parent reply other threads:[~2017-01-06 16:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 16:10 [Intel-wired-lan] [next PATCH 00/11] igb: Add support for writable pages and build_skb Alexander Duyck
2017-01-06 16:10 ` [Intel-wired-lan] [next PATCH 1/9] igb: Add support for DMA_ATTR_WEAK_ORDERING Alexander Duyck
2017-01-06 16:10 ` [Intel-wired-lan] [next PATCH 2/9] igb: Use length to determine if descriptor is done Alexander Duyck
2017-01-10 9:13 ` Brown, Aaron F
2017-01-06 16:10 ` [Intel-wired-lan] [next PATCH 3/9] igb: Clear Rx buffer_info in configure instead of clean Alexander Duyck
2017-01-06 16:11 ` [Intel-wired-lan] [next PATCH 4/9] igb: Don't bother clearing Tx buffer_info in igb_clean_tx_ring Alexander Duyck
2017-01-06 16:11 ` [Intel-wired-lan] [next PATCH 5/9] igb: Limit maximum frame Rx based on MTU Alexander Duyck
2017-01-06 16:11 ` [Intel-wired-lan] [next PATCH 6/9] igb: Add support for padding packet Alexander Duyck
2017-01-06 16:11 ` [Intel-wired-lan] [next PATCH 7/9] igb: Add support for ethtool private flag to allow use of legacy Rx Alexander Duyck
2017-01-06 16:11 ` [Intel-wired-lan] [next PATCH 8/9] igb: Break out Rx buffer page management Alexander Duyck
2017-01-06 16:11 ` [Intel-wired-lan] [next PATCH 9/9] igb: Revert "igb: Revert support for build_skb in igb" Alexander Duyck
2017-01-06 16:39 ` Jeff Kirsher [this message]
2017-01-06 17:10 ` Duyck, Alexander H
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=1483720797.25700.60.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.