All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Jero <sj323707@ohio.edu>
To: dccp@vger.kernel.org
Subject: Testing Tree Timeline
Date: Mon, 13 Jun 2011 16:15:36 +0000	[thread overview]
Message-ID: <4DF637A8.5090104@ohio.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]

Hello All,

I was wondering what the current timeline looks like for integrating the
patches in the testing tree into the mainline kernel?

Myself, and several other researchers at Ohio University, believe that
DCCP would be an ideal protocol for encapsulating Delay Tolerant
Networking protocols for transportation across the Internet. For testing
purposes, we do not desire guaranteed reliability, but do require
congestion control.

After testing (and bug fixing) DCCP for most of the last year, we are
convinced that DCCP with CCID2 will be effective for our goals. In fact,
we are in the process of writing an Internet Draft to recommend that
other researchers use DCCP for encapsulating these DTN protocols.

However, the CCID2 code in the mainline kernel is very buggy and suffers
from very poor performance. As a result, the only way to get a version
of CCID2 that works well is to build a custom kernel from the testing
tree. This, obviously, puts a damper on adoption.

As a result, it would be nice to have some idea of when code typically
migrates from the testing tree into the mainline kernel and how that
determination is made.

Thanks.

Samuel Jero
Internetworking Research Group
Ohio University


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

             reply	other threads:[~2011-06-13 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13 16:15 Samuel Jero [this message]
2011-06-13 20:21 ` Testing Tree Timeline Ian McDonald
2011-06-15  5:10 ` Gerrit Renker

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=4DF637A8.5090104@ohio.edu \
    --to=sj323707@ohio.edu \
    --cc=dccp@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 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.