From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wen Congyang Subject: Re: [PATCH 02/13 V6] remus: implement network buffering hotplug scripts Date: Mon, 27 Jan 2014 15:06:16 +0800 Message-ID: <52E60568.7060305@cn.fujitsu.com> References: <1390295117-718-1-git-send-email-laijs@cn.fujitsu.com> <1390295117-718-3-git-send-email-laijs@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: rshriram@cs.ubc.ca, Lai Jiangshan Cc: Ian Campbell , Stefano Stabellini , Andrew Cooper , Jiang Yunhong , Ian Jackson , "xen-devel@lists.xen.org" , Dong Eddie , Roger Pau Monne List-Id: xen-devel@lists.xenproject.org At 01/27/2014 06:27 AM, Shriram Rajagopalan Wrote: > On Tue, Jan 21, 2014 at 1:05 AM, Lai Jiangshan wrote: > >> From: Shriram Rajagopalan >> >> This patch introduces remus-netbuf-setup hotplug script responsible for >> setting up and tearing down the necessary infrastructure required for >> network output buffering in Remus. This script is intended to be invoked >> by libxl for each guest interface, when starting or stopping Remus. >> >> Apart from returning success/failure indication via the usual hotplug >> entries in xenstore, this script also writes to xenstore, the name of >> the IFB device to be used to control the vif's network output. >> >> The script relies on libnl3 command line utilities to perform various >> setup/teardown functions. The script is confined to Linux platforms only >> since NetBSD does not seem to have libnl3. >> >> Signed-off-by: Shriram Rajagopalan >> Signed-off-by: Lai Jiangshan >> Reviewed-by: Wen Congyang >> --- >> tools/hotplug/Linux/Makefile | 1 + >> tools/hotplug/Linux/remus-netbuf-setup | 183 >> +++++++++++++++++++++++++++++++++ >> 2 files changed, 184 insertions(+) >> create mode 100644 tools/hotplug/Linux/remus-netbuf-setup >> >> > The last time I posted this script, the feedback was that the script and > the code invoking > the script should be in a single patch. So I would suggest doing the same. We use the script in patch6. It adds 479 lines. These two patches are big patches(add more than 100 lines), so why put them into a single patch? Thanks Wen Congyang > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >