From: Varka Bhadram <varkabhadram@gmail.com>
To: Pravin B Shelar <pshelar@nicira.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org, Alex Wang <alexw@nicira.com>
Subject: Re: [PATCH net-next v7 1/6] openvswitch: Allow each vport to have an array of 'port_id's.
Date: Tue, 22 Jul 2014 12:23:35 +0530 [thread overview]
Message-ID: <53CE0A6F.9030403@gmail.com> (raw)
In-Reply-To: <1406010583-1746-1-git-send-email-pshelar@nicira.com>
On 07/22/2014 11:59 AM, Pravin B Shelar wrote:
> From: Alex Wang <alexw@nicira.com>
>
> In order to allow handlers directly read upcalls from datapath,
> we need to support per-handler netlink socket for each vport in
> datapath. This commit makes this happen. Also, it is guaranteed
> to be backward compatible with previous branch.
>
> Signed-off-by: Alex Wang <alexw@nicira.com>
> Acked-by: Thomas Graf <tgraf@redhat.com>
> Signed-off-by: Pravin B Shelar <pshelar@nicira.com>
> ---
> include/uapi/linux/openvswitch.h | 13 ++++--
> net/openvswitch/datapath.c | 21 ++++++---
> net/openvswitch/vport.c | 99 +++++++++++++++++++++++++++++++++++++++-
> net/openvswitch/vport.h | 27 +++++++++--
> 4 files changed, 144 insertions(+), 16 deletions(-)
WARNING: line over 80 characters
#67: FILE: net/openvswitch/datapath.c:1635:
+ nla_put_string(skb, OVS_VPORT_ATTR_NAME, vport->ops->get_name(vport)))
WARNING: line over 80 characters
#99: FILE: net/openvswitch/datapath.c:1820:
+ a[OVS_VPORT_ATTR_UPCALL_PID]);
WARNING: line over 80 characters
#226: FILE: net/openvswitch/vport.c:423:
+ return ids->ids[hash - ids->n_ids * reciprocal_divide(hash, ids->rn_ids)];
--
Regards,
Varka Bhadram.
prev parent reply other threads:[~2014-07-22 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 6:29 [PATCH net-next v7 1/6] openvswitch: Allow each vport to have an array of 'port_id's Pravin B Shelar
2014-07-22 6:53 ` Varka Bhadram [this message]
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=53CE0A6F.9030403@gmail.com \
--to=varkabhadram@gmail.com \
--cc=alexw@nicira.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).