From: Vlad Yasevich <vyasevic@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.com
Subject: Re: [RFC PATCH 01/13] net: Add generic packet offload infrastructure.
Date: Wed, 14 Nov 2012 08:03:42 -0500 [thread overview]
Message-ID: <50A396AE.5090608@redhat.com> (raw)
In-Reply-To: <1352859861.4497.0.camel@edumazet-glaptop>
On 11/13/2012 09:24 PM, Eric Dumazet wrote:
> On Tue, 2012-11-13 at 20:24 -0500, Vlad Yasevich wrote:
>> Create a new data structure to contain the GRO/GSO callbacks and add
>> a new registration mechanism.
>>
>> Singed-off-by: Vlad Yasevich <vyasevic@redhat.com>
>> ---
>> include/linux/netdevice.h | 15 ++++++++
>> net/core/dev.c | 80 +++++++++++++++++++++++++++++++++++++++++++++
>> 2 files changed, 95 insertions(+), 0 deletions(-)
>>
>> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
>> index f8eda02..d15af51 100644
>> --- a/include/linux/netdevice.h
>> +++ b/include/linux/netdevice.h
>> @@ -1511,6 +1511,18 @@ struct packet_type {
>> struct list_head list;
>> };
>>
>> +struct packet_offload {
>> + __be16 type; /* This is really htons(ether_type). */
>> + struct net_device *dev; /* NULL is wildcarded here */
>
> Shouldnt this dev pointer be removed at some point in the patch serie ?
yes. i was thinking about this as well. I actually shouldn't have been
carried into this struct to begin with since its not really being used
by the offload calls.
-vlad
>
>> + struct sk_buff *(*gso_segment)(struct sk_buff *skb,
>> + netdev_features_t features);
>> + int (*gso_send_check)(struct sk_buff *skb);
>> + struct sk_buff **(*gro_receive)(struct sk_buff **head,
>> + struct sk_buff *skb);
>> + int (*gro_complete)(struct sk_buff *skb);
>> + struct list_head list;
>> +};
>> +
>> #include <linux/notifier.h>
>>
>
next prev parent reply other threads:[~2012-11-14 13:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 1:24 [RFC PATCH 00/13] Always build GSO/GRO functionality into the kernel Vlad Yasevich
2012-11-14 1:24 ` [RFC PATCH 01/13] net: Add generic packet offload infrastructure Vlad Yasevich
2012-11-14 2:24 ` Eric Dumazet
2012-11-14 13:03 ` Vlad Yasevich [this message]
2012-11-14 1:24 ` [RFC PATCH 02/13] core: Switch to using the new packet offload infrustructure Vlad Yasevich
2012-11-14 1:24 ` [RFC PATCH 03/13] net: Add net protocol offload registration infrustructure Vlad Yasevich
2012-11-14 8:22 ` Nicolas Dichtel
2012-11-14 13:08 ` Vlad Yasevich
2012-11-14 23:14 ` Francois Romieu
2012-11-15 2:16 ` Vlad Yasevich
2012-11-14 1:24 ` [RFC PATCH 04/13] ipv6: Add new offload registration infrastructure Vlad Yasevich
2012-11-14 1:24 ` [RFC PATCH 05/13] ipv4: Switch to using the new offload infrastructure Vlad Yasevich
2012-11-14 1:24 ` [RFC PATCH 06/13] ipv6: Switch to using " Vlad Yasevich
2012-11-14 1:24 ` [RFC PATCH 07/13] ipv6: Separate ipv6 offload support Vlad Yasevich
2012-11-14 1:24 ` [RFC PATCH 08/13] ipv6: Separate tcp offload functionality Vlad Yasevich
2012-11-14 1:24 ` [RFC PATCH 09/13] ipv6: Separate out UDP " Vlad Yasevich
2012-11-14 1:24 ` [RFC PATCH 10/13] ipv6: Move exthdr offload support into separate file Vlad Yasevich
2012-11-14 1:24 ` [RFC PATCH 11/13] ipv6: Update ipv6 static library with newly needed functions Vlad Yasevich
2012-11-14 1:24 ` [RFC PATCH 12/13] ipv4: Pull GSO registration out of inet_init() Vlad Yasevich
2012-11-14 1:24 ` [RFC PATCH 13/13] ipv6: Pull IPv6 GSO registration out of the module Vlad Yasevich
2012-11-16 22:04 ` Ben Hutchings
2012-11-14 2:25 ` [RFC PATCH 00/13] Always build GSO/GRO functionality into the kernel Eric Dumazet
2012-11-14 13:10 ` Vlad Yasevich
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=50A396AE.5090608@redhat.com \
--to=vyasevic@redhat.com \
--cc=davem@davemloft.com \
--cc=eric.dumazet@gmail.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).