From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: davem@davemloft.net
Cc: dccp@vger.kernel.org, netdev@vger.kernel.org
Subject: net-next-2.6 [PATCH 0/2] dccp: Policy-based packet dequeueing interface
Date: Mon, 6 Dec 2010 08:44:02 +0100 [thread overview]
Message-ID: <1291621444-5927-1-git-send-email-gerrit@erg.abdn.ac.uk> (raw)
In-Reply-To: <dccp_net_next_2_6__packet_dequeueing_interface>
Hi Dave,
please find attached a self-contained 2-patch set by Tomasz which adds an API
to influence DCCP packet dequeueing. It evolved from discussions in 2008,
adding and adds basic building blocks for sending congestion controlled
multimedia packets that have a priority or a deadline attached to them.
Occasionally people still make new suggestions for such an API, apparently
overlooking the excellent work Tomasz has done and which has been in the
test tree for two years.
Patch #1: introduces the new policy-based packet dequeueing infrastructure.
Patch #2: adds parameter (sanity) checking of cmsg qpolicy parameters.
I have also placed this in into a fresh (today's) copy of net-next-2.6, on
git://eden-feed.erg.abdn.ac.uk/net-next-2.6 [subtree 'dccp']
The set is fully bisectable.
---
Documentation/networking/dccp.txt | 20 ++++++
include/linux/dccp.h | 21 ++++++
net/dccp/Makefile | 4 +-
net/dccp/dccp.h | 13 ++++
net/dccp/output.c | 7 +-
net/dccp/proto.c | 71 ++++++++++++++++++-
net/dccp/qpolicy.c | 137 +++++++++++++++++++++++++++++++++++++
7 files changed, 264 insertions(+), 9 deletions(-)
next parent reply other threads:[~2010-12-06 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dccp_net_next_2_6__packet_dequeueing_interface>
2010-12-06 7:44 ` Gerrit Renker [this message]
2010-12-06 7:44 ` [PATCH 1/2] dccp: Policy-based packet dequeueing infrastructure Gerrit Renker
2010-12-08 18:01 ` net-next-2.6 [PATCH 0/2] dccp: Policy-based packet dequeueing interface David Miller
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=1291621444-5927-1-git-send-email-gerrit@erg.abdn.ac.uk \
--to=gerrit@erg.abdn.ac.uk \
--cc=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
--cc=netdev@vger.kernel.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).