public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jesse Gross <jesse@nicira.com>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, dev@openvswitch.org,
	Pravin B Shelar <pshelar@nicira.com>
Subject: Re: [PATCH net-next 04/11] openvswitch: Restructure datapath.c and flow.c
Date: Tue, 29 Oct 2013 18:25:13 -0700	[thread overview]
Message-ID: <1383096313.12439.44.camel@joe-AO722> (raw)
In-Reply-To: <1383092544-50599-5-git-send-email-jesse@nicira.com>

On Tue, 2013-10-29 at 17:22 -0700, Jesse Gross wrote:
> Over the time datapath.c and flow.c has became pretty large files.
> Following patch restructures functionality of component into three
> different components:
[]
>  net/openvswitch/Makefile       |    2 +
>  net/openvswitch/datapath.c     |  528 +------------
>  net/openvswitch/datapath.h     |    1 +
>  net/openvswitch/flow.c         | 1605 +---------------------------------------
>  net/openvswitch/flow.h         |  128 +---
>  net/openvswitch/flow_netlink.c | 1603 +++++++++++++++++++++++++++++++++++++++

Is this largish patch any different or easier to
read/verify when generated with git format-patch -M ?

  reply	other threads:[~2013-10-30  1:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30  0:22 [GIT net-next] Open vSwitch Jesse Gross
2013-10-30  0:22 ` [PATCH net-next 01/11] openvswitch: Move flow table rehashing to flow install Jesse Gross
     [not found] ` <1383092544-50599-1-git-send-email-jesse-l0M0P4e3n4LQT0dZR+AlfA@public.gmane.org>
2013-10-30  0:22   ` [PATCH net-next 02/11] openvswitch: remove duplicated include from vport-vxlan.c Jesse Gross
2013-10-30  0:22 ` [PATCH net-next 03/11] openvswitch: remove duplicated include from vport-gre.c Jesse Gross
2013-10-30  0:22 ` [PATCH net-next 04/11] openvswitch: Restructure datapath.c and flow.c Jesse Gross
2013-10-30  1:25   ` Joe Perches [this message]
2013-10-30  1:32     ` Joe Perches
2013-10-30  0:22 ` [PATCH net-next 05/11] openvswitch: Move mega-flow list out of rehashing struct Jesse Gross
2013-10-30  0:22 ` [PATCH net-next 06/11] openvswitch: Simplify mega-flow APIs Jesse Gross
2013-10-30  0:22 ` [PATCH net-next 07/11] openvswitch: collect mega flow mask stats Jesse Gross
2013-10-30  0:22 ` [PATCH net-next 08/11] openvswitch: Per cpu flow stats Jesse Gross
     [not found]   ` <1383092544-50599-9-git-send-email-jesse-l0M0P4e3n4LQT0dZR+AlfA@public.gmane.org>
2013-10-30  2:11     ` David Miller
     [not found]       ` <20131029.221125.343749464995759893.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2013-11-02 21:51         ` Jesse Gross
2013-10-30  0:22 ` [PATCH net-next 09/11] openvswitch: Enable all GSO features on internal port Jesse Gross
2013-10-30  0:22 ` [PATCH net-next 10/11] openvswitch: Widen TCP flags handling Jesse Gross
2013-10-30  0:22 ` [PATCH net-next 11/11] openvswitch: TCP flags matching support Jesse Gross
  -- strict thread matches above, loose matches on Subject: below --
2013-11-02  7:43 [GIT net-next] Open vSwitch Jesse Gross
2013-11-02  7:43 ` [PATCH net-next 04/11] openvswitch: Restructure datapath.c and flow.c Jesse Gross

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=1383096313.12439.44.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=jesse@nicira.com \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.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