From: Govindarajulu Varadarajan <_govind@gmx.com>
To: Chema Gonzalez <chema@berkeley.edu>
Cc: Govindarajulu Varadarajan <_govind@gmx.com>,
davem@davemloft.net, netdev <netdev@vger.kernel.org>,
ssujith@cisco.com, gvaradar@cisco.com, benve@cisco.com
Subject: Re: [PATCH net-next 1/8] flow_keys: Record IP layer protocol in skb_flow_dissect()
Date: Fri, 20 Jun 2014 00:22:22 +0530 (IST) [thread overview]
Message-ID: <alpine.LNX.2.03.1406200018500.7347@ws.cisco> (raw)
In-Reply-To: <CAEb0Mfc6Q5uO2dexTtsT4paXpqHKKGfJimgX0Wipebapncv5hw@mail.gmail.com>
On Thu, 19 Jun 2014, Chema Gonzalez wrote:
> If you add n_proto, have you considered adding nhoff too? That way the
> L3 and L4 headers will be completely pinned by the flow dissector.
>
Yes, I have actually considered it. But right now there is no one who would need
nhoff. We can add it later when we need it?
Thanks
next prev parent reply other threads:[~2014-06-19 18:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 18:32 [PATCH net-next 0/8] enic updates Govindarajulu Varadarajan
2014-06-09 18:32 ` [PATCH net-next 1/8] flow_keys: Record IP layer protocol in skb_flow_dissect() Govindarajulu Varadarajan
2014-06-10 13:11 ` Daniel Borkmann
2014-06-10 14:08 ` Govindarajulu Varadarajan
2014-06-10 14:26 ` Eric Dumazet
2014-06-11 22:06 ` David Miller
2014-06-11 22:08 ` David Miller
2014-06-12 5:38 ` Govindarajulu Varadarajan
2014-06-19 18:06 ` Chema Gonzalez
2014-06-19 18:52 ` Govindarajulu Varadarajan [this message]
2014-06-24 5:29 ` Yinghai Lu
2014-06-26 6:34 ` Govindarajulu Varadarajan
2014-09-18 14:18 ` Or Gerlitz
2014-09-18 14:38 ` Eric Dumazet
2014-09-18 15:02 ` [PATCH net] net: sched: shrink struct qdisc_skb_cb to 28 bytes Eric Dumazet
2014-09-18 16:26 ` Stephen Hemminger
2014-09-18 16:32 ` Eric Dumazet
2014-09-18 18:00 ` Eric Dumazet
2014-09-18 18:07 ` Joe Perches
2014-09-18 19:14 ` Eric Dumazet
2014-09-18 19:31 ` Joe Perches
2014-09-18 20:31 ` Eric Dumazet
2014-09-18 21:28 ` Or Gerlitz
2014-09-18 22:29 ` [net] " Doug Ledford
2014-09-19 12:07 ` Or Gerlitz
2014-09-22 18:38 ` David Miller
2014-09-22 18:22 ` [PATCH net] " David Miller
2014-06-09 18:32 ` [PATCH net-next 2/8] enic: fix return value in _vnic_dev_cmd Govindarajulu Varadarajan
2014-06-09 18:32 ` [PATCH net-next 3/8] enic: devcmd for adding IP 5 tuple hardware filters Govindarajulu Varadarajan
2014-06-09 18:32 ` [PATCH net-next 4/8] enic: alloc/free rx_cpu_rmap Govindarajulu Varadarajan
2014-06-09 18:44 ` Sergei Shtylyov
2014-06-10 13:52 ` Govindarajulu Varadarajan
2014-06-10 15:00 ` Sergei Shtylyov
2014-06-09 18:32 ` [PATCH net-next 5/8] enic: Add Accelerated RFS support Govindarajulu Varadarajan
2014-06-09 18:32 ` [PATCH net-next 6/8] enic: fix lockdep around devcmd_lock Govindarajulu Varadarajan
2014-06-09 18:32 ` [PATCH net-next 7/8] enic: add low latency socket busy_poll support Govindarajulu Varadarajan
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=alpine.LNX.2.03.1406200018500.7347@ws.cisco \
--to=_govind@gmx.com \
--cc=benve@cisco.com \
--cc=chema@berkeley.edu \
--cc=davem@davemloft.net \
--cc=gvaradar@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=ssujith@cisco.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 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).