From: Hongyang Yang <yanghy@cn.fujitsu.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: eddie.dong@intel.com, wency@cn.fujitsu.com,
stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
yunhong.jiang@intel.com, ian.jackson@eu.citrix.com,
xen-devel@lists.xen.org, rshriram@cs.ubc.ca,
laijs@cn.fujitsu.com, roger.pau@citrix.com
Subject: Re: [PATCH v14 2/7] remus: add libnl3 dependency for network buffering support
Date: Thu, 3 Jul 2014 18:31:35 +0800 [thread overview]
Message-ID: <53B53107.6030309@cn.fujitsu.com> (raw)
In-Reply-To: <1404381809.14865.38.camel@kazak.uk.xensource.com>
Hi Ian,
On 07/03/2014 06:03 PM, Ian Campbell wrote:
> On Wed, 2014-07-02 at 16:09 +0800, Yang Hongyang wrote:
>> Libnl3 is required for controlling Remus network buffering.
>> This patch adds dependency on libnl3 (>= 3.2.8) to autoconf scripts.
>> Also provide ability to configure tools without libnl3 support, that
>> is without network buffering support.
>>
>> when there's no network buffering support,libxl__netbuffer_enabled()
>> returns 0, otherwise returns 1. The callers of this api will be
>> introduced in the rest of the series.
>>
>> NOTE: This patch changes tools/configure.ac, please rerun
>> autogen.sh while apply the patch.
>> Signed-off-by: Shriram Rajagopalan <rshriram@cs.ubc.ca>
>> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
>> Signed-off-by: Yang Hongyang <yanghy@cn.fujitsu.com>
>> Reviewed-by: Wen Congyang <wency@cn.fujitsu.com>
>> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
>
> I considered applying this but I suppose it isn't all that useful
> without the rest of the remus stuff so it might as well wait. Thoughts?
Agreed.
>
> Perhaps someone might like to consider modifying ts-xen-build-prep and
> ts-xen-install in http://xenbits.xen.org/gitweb/?p=osstest.git to add
> whichever Debian packages provide the development headers and runtime
> dependencies respectively?
>
> (that is, add the libfoo-dev to ts-xen-build-prep and the libfoo to
> ts-xen-install)
I can take a look at this although I'm not familiar with osstest...
>
> Ian.
>
> .
>
--
Thanks,
Yang.
next prev parent reply other threads:[~2014-07-03 10:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 8:09 [PATCH v14 0/7] Remus/Libxl: Remus network buffering and drbd disk Yang Hongyang
2014-07-02 8:09 ` [PATCH v14 1/7] remus: make postcopy callback asynchronous Yang Hongyang
2014-07-03 10:03 ` Ian Campbell
2014-07-02 8:09 ` [PATCH v14 2/7] remus: add libnl3 dependency for network buffering support Yang Hongyang
2014-07-03 10:03 ` Ian Campbell
2014-07-03 10:31 ` Hongyang Yang [this message]
2014-07-02 8:09 ` [PATCH v14 3/7] remus: introduce remus device Yang Hongyang
2014-07-02 8:09 ` [PATCH v14 4/7] remus netbuffer: implement remus network buffering for nic devices Yang Hongyang
2014-07-02 8:09 ` [PATCH v14 5/7] remus drbd: Implement remus drbd replicated disk Yang Hongyang
2014-07-02 8:09 ` [PATCH v14 6/7] libxl: network buffering cmdline switch Yang Hongyang
2014-07-02 8:09 ` [PATCH v14 7/7] libxl: disk " Yang Hongyang
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=53B53107.6030309@cn.fujitsu.com \
--to=yanghy@cn.fujitsu.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=ian.jackson@eu.citrix.com \
--cc=laijs@cn.fujitsu.com \
--cc=roger.pau@citrix.com \
--cc=rshriram@cs.ubc.ca \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xen.org \
--cc=yunhong.jiang@intel.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 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.