Hi Ben, TCS has a team working on the vacancy events feature. Shashwat and Sandeep are part of that team and have contributed some part of code in this patch. That is why there name has been added in the signoff chain.
I am reposting version 3 of the patch rebased with latest master for your reference. Please provide your feedback on the same. Thanks and Regards, Saloni Jain Tata Consultancy Services Mailto: saloni.j...@tcs.com Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Consulting ____________________________________________ -----"dev" <dev-boun...@openvswitch.org> wrote: ----- To: saloni.jai...@gmail.com From: Ben Pfaff Sent by: "dev" Date: 08/22/2015 03:37AM Cc: dev@openvswitch.org, Shashwat Srivastava <shashwat.srivast...@tcs.com>, deepankar.gu...@tcs.com, partha.da...@tcs.com, Sandeep Kumar <sandeep.kuma...@tcs.com> Subject: Re: [ovs-dev] [PATCH v2 1/3] Implement Openflow 1.4 Vacancy Events for OFPT_TABLE_MOD. On Wed, Aug 19, 2015 at 12:53:16PM +0530, saloni.jai...@gmail.com wrote: > From: Saloni Jain <saloni.j...@tcs.com> > > OpenFlow 1.4 introduces the ability to turn on vacancy events with an > OFPT_TABLE_MOD message specifying OFPTC_VACANCY_EVENTS. This commit adds > support for the new feature in ovs-ofctl mod-table. > As per the openflow specification-1.4, vacancy event adds a mechanism > enabling the controller to get an early warning based on capacity > threshold chosen by the controller. > > With this commit, vacancy events can be configured as: > ovs-ofctl -O OpenFlow14 mod-table <bridge> <table> vacancy-<range> > The syntax of <range> as <low..high>. > <range> specify vacancy threshold values, vacancy down and vacancy up. > > To disable vacancy events, following command should be given: > ovs-ofctl -O OpenFlow14 mod-table <bridge> <table> novacancy > > Signed-off-by: Saloni Jain <saloni.j...@tcs.com> > Signed-off-by: Shashwat Srivastava <shashwat.srivast...@tcs.com> > Signed-off-by: Sandeep Kumar <sandeep.kuma...@tcs.com> Please explain the signoff chain. Presumably, you are the author. As the person providing the patch, that means you need to be the final signoff. Who are Shashwat and Sandeep? _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
