From: David Miller <davem@davemloft.net>
To: rshriram@cs.ubc.ca
Cc: netdev@vger.kernel.org, jhs@mojatatu.com, hagen@jauu.net,
brendan@cs.ubc.ca
Subject: Re: [PATCH V3] net/sched: sch_plug - Queue traffic until an explicit release command
Date: Tue, 07 Feb 2012 12:57:45 -0500 (EST) [thread overview]
Message-ID: <20120207.125745.676129087240196385.davem@davemloft.net> (raw)
In-Reply-To: <1328485892-16721-1-git-send-email-rshriram@cs.ubc.ca>
From: rshriram@cs.ubc.ca
Date: Sun, 5 Feb 2012 15:51:32 -0800
> From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
>
> The qdisc supports two operations - plug and unplug. When the
> qdisc receives a plug command via netlink request, packets arriving
> henceforth are buffered until a corresponding unplug command is received.
> Depending on the type of unplug command, the queue can be unplugged
> indefinitely or selectively.
>
> This qdisc can be used to implement output buffering, an essential
> functionality required for consistent recovery in checkpoint based
> fault-tolerance systems. Output buffering enables speculative execution
> by allowing generated network traffic to be rolled back. It is used to
> provide network protection for Xen Guests in the Remus high availability
> project, available as part of Xen.
>
> This module is generic enough to be used by any other system that wishes
> to add speculative execution and output buffering to its applications.
>
> This module was originally available in the linux 2.6.32 PV-OPS tree,
> used as dom0 for Xen.
>
> For more information, please refer to http://nss.cs.ubc.ca/remus/
> and http://wiki.xensource.com/xenwiki/Remus
>
> Changes in V3:
> * Removed debug output (printk) on queue overflow
> * Added TCQ_PLUG_RELEASE_INDEFINITE - that allows the user to
> use this qdisc, for simple plug/unplug operations.
> * Use of packet counts instead of pointers to keep track of
> the buffers in the queue.
>
> Signed-off-by: Shriram Rajagopalan <rshriram@cs.ubc.ca>
> Signed-off-by: Brendan Cully <brendan@cs.ubc.ca>
> [author of the code in the linux 2.6.32 pvops tree]
Applied, thanks.
prev parent reply other threads:[~2012-02-07 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 23:51 [PATCH V3] net/sched: sch_plug - Queue traffic until an explicit release command rshriram
2012-02-07 17:57 ` David Miller [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=20120207.125745.676129087240196385.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brendan@cs.ubc.ca \
--cc=hagen@jauu.net \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=rshriram@cs.ubc.ca \
/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).