qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Shivam Mehra <mshivam2196@gmail.com>,
	qemu-devel@nongnu.org, qemu-discuss@nongnu.org, "Zhang,
	Chen" <chen.zhang@intel.com>
Subject: Re: network buffering in fault tolerance
Date: Thu, 15 Oct 2020 15:31:55 +0800	[thread overview]
Message-ID: <3e025aed-c3c3-88f9-8ef9-d18cde6e9568@redhat.com> (raw)
In-Reply-To: <CANp2S64q_MEp6MWuYvt2iNFq4kKZQ+3xOhVhbQ0AqD9CrQqcSQ@mail.gmail.com>


On 2020/9/30 下午1:12, Shivam Mehra wrote:
>
> I came across this documentation with source code for providing 
> network buffering to applications 
> https://www.nfradead.org/~tgr/libnl/doc/api/route_2qdisc_2plug_8c_source.html 
> <https://www.infradead.org/~tgr/libnl/doc/api/route_2qdisc_2plug_8c_source.html>. 
> This network-buffering helps output-commit problem when providing 
> fault tolerance to virtual machines. The output is buffered until an 
> acknowledgement arrives from the backup VM and then released to the 
> external world. So that backup and primary VMs seem consistent 
> externally. Initially developed for XEN VMM to provide fault tolerance 
> to VMs and I think it's now available for |QEMU| too.
>
> Where does the script reside which does network-buffering for 
> checkpoints? and what are the commands to make this happen?
>
> I want to do this network-buffering for packets originating from an 
> application. Is it possible to do it in the same way as above? Does it 
> do any damage to the host kernel? Can I get  a simple working example 
> for this?
>

Hi Shivam:

I haven't gone through the qdisc you mentioned, but it depends on a 
specific host network setup to work if I understand correctly.

Qemu support a native HA (COLO) which has a buffer filter.

Cc Chen for more information.

Thanks



      reply	other threads:[~2020-10-15  7:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30  5:12 network buffering in fault tolerance Shivam Mehra
2020-10-15  7:31 ` Jason Wang [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=3e025aed-c3c3-88f9-8ef9-d18cde6e9568@redhat.com \
    --to=jasowang@redhat.com \
    --cc=chen.zhang@intel.com \
    --cc=mshivam2196@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.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 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).