DCCP protocol discussions
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: dccp@vger.kernel.org
Subject: Re: [RFC] CCID infrastructure improvements
Date: Thu, 16 Feb 2006 02:50:21 +0000	[thread overview]
Message-ID: <39e6f6c70602151850g76ac2dcfy57dc4155dd033294@mail.gmail.com> (raw)
In-Reply-To: <39e6f6c70602151022v2d63a9d3nf88c0db59bfa36e9@mail.gmail.com>

On 2/15/06, Ian McDonald <imcdnzl@gmail.com> wrote:
> On 2/16/06, Arnaldo Carvalho de Melo <acme@ghostprotocols.net> wrote:
> > Hi Ian, Andrea,
> >
> >        Can somebody please poke holes in the attached patch? It moves
> > more code out of the
> > CCIDs into the CCID infrastructure, simplifying some stuff.
> >
> >        With this rework ccid_operations becomes the struct proto
> > counterpart in ccid land (struct sock has a "operations" pointer to
> > struct proto).
> >
> >        I saw the need for this when working on Andrea's ccid feature
> > negotiation patch, that I'm
> > now reworking to take advantage of the attached patch.
> >
> As a baseline I downloaded acme-net-2.6.17.git and did some testing.
> When I test with netem in the middle between two boxes the transmitter
> locks solid....
>
> Test
> ./ttcp_acme -c -l500 -n100 -t jandi2
> ./ttcp_acme -c -l500 -r
>
> Netem configured as follows in middle box:
> sudo tc qdisc add dev lan1 root netem delay 50ms loss 10%
> sudo tc qdisc add dev lan0 root netem delay 50ms loss 10%
>
> I don't believe this happens with older version of DCCP (just pre
> CCID2) so I will start trying to track down....
>
> I don't have so much time so may take a little while. Feel free to
> investigate earlier if you wish.
>
> As such I haven't tested the patch as baseline not stable...
>

http://master.kernel.org/git/?p=linux/kernel/git/acme/net-2.6.17.git;a=shortlog;hÌid_operations

I tested with the code that is in the "ccid_operations" of my
net-2.6.17 git tree (can
you give it a try? Perhaps I did some last minute fix over the one you tested),
but without a middle box, tomorrow I'll revive this parisc and use
another machine
to test on real machines, not just qemu.

- Arnaldo

  parent reply	other threads:[~2006-02-16  2:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 18:22 [RFC] CCID infrastructure improvements Arnaldo Carvalho de Melo
2006-02-16  1:18 ` Ian McDonald
2006-02-16  2:50 ` Arnaldo Carvalho de Melo [this message]
2006-02-16  2:56 ` Ian McDonald

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=39e6f6c70602151850g76ac2dcfy57dc4155dd033294@mail.gmail.com \
    --to=acme@ghostprotocols.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox