From: David Miller <davem@davemloft.net>
To: pshelar@nicira.com
Cc: netdev@vger.kernel.org
Subject: Re: [GIT net-next v3] Open vSwitch
Date: Tue, 16 Sep 2014 16:25:59 -0400 (EDT) [thread overview]
Message-ID: <20140916.162559.345926762747823937.davem@davemloft.net> (raw)
In-Reply-To: <1410852209-1456-1-git-send-email-pshelar@nicira.com>
From: Pravin B Shelar <pshelar@nicira.com>
Date: Tue, 16 Sep 2014 00:23:29 -0700
> Following patches adds recirculation and hash action to OVS.
> First patch removes pointer to stack object. Next three patches
> does code restructuring which is required for last patch.
> Recirculation implementation is changed, according to comments from
> David Miller, to avoid using recursive calls in OVS. It is using
> queue to record recirc action and deferred recirc is executed at
> the end of current actions execution.
>
> v1-v2:
> Changed subsystem name in subject to openvswitch
> v2-v3:
> Added patch to remove pkt_key pointer from skb->cb.
Pulled, thanks Pravin.
next prev parent reply other threads:[~2014-09-16 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 7:23 [GIT net-next v3] Open vSwitch Pravin B Shelar
2014-09-16 20:25 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-16 7:30 Pravin B Shelar
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=20140916.162559.345926762747823937.davem@davemloft.net \
--to=davem@davemloft.net \
--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