All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Stringer <joe@ovn.org>
To: Andy Zhou <azhou@ovn.org>
Cc: netdev <netdev@vger.kernel.org>, pravin shelar <pshelar@ovn.org>
Subject: Re: [RFC net-next sample action optimization 1/3] openvswitch: deferred fifo api change
Date: Thu, 9 Mar 2017 11:08:34 -0800	[thread overview]
Message-ID: <CAPWQB7GyKezwgjkGs3bm3W_cXMkGyy=5bW_xMpcB8Wb7kZh0nQ@mail.gmail.com> (raw)
In-Reply-To: <1488932137-120383-2-git-send-email-azhou@ovn.org>

On 7 March 2017 at 16:15, Andy Zhou <azhou@ovn.org> wrote:
> add_deferred_actions() API currently requires actions to be passed in
> as a fully encoded netlink message. So far both 'sample' and 'recirc'
> actions happens to carry actions as fully encoded netlink messages.
> However, this requirement is more restrictive than necessary, future
> patch will need to pass in action lists that are not fully encoded
> by themselves.
>
> Signed-off-by: Andy Zhou <azhou@ovn.org>

Acked-by: Joe Stringer <joe@ovn.org>

  reply	other threads:[~2017-03-09 19:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  0:15 [RFC net-next sample action optimization 0/3] Andy Zhou
2017-03-08  0:15 ` [RFC net-next sample action optimization 1/3] openvswitch: deferred fifo api change Andy Zhou
2017-03-09 19:08   ` Joe Stringer [this message]
2017-03-08  0:15 ` [RFC net-next sample action optimization 2/3] openvswitch: Refactor recirc key allocation Andy Zhou
2017-03-09 19:11   ` Joe Stringer
2017-03-10 21:44     ` Andy Zhou
2017-03-08  0:15 ` [RFC net-next sample action optimization 3/3] openvswitch: Optimize sample action for the clone use cases Andy Zhou
2017-03-09 19:46   ` Joe Stringer
2017-03-10 22:07     ` Andy Zhou
2017-03-10 23:12       ` Joe Stringer

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='CAPWQB7GyKezwgjkGs3bm3W_cXMkGyy=5bW_xMpcB8Wb7kZh0nQ@mail.gmail.com' \
    --to=joe@ovn.org \
    --cc=azhou@ovn.org \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@ovn.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.