From: David Miller <davem@davemloft.net>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 0/7] [DCCP]: Fixes and enhancements
Date: Sun, 27 Aug 2006 02:08:51 +0000 [thread overview]
Message-ID: <20060826.190851.74747699.davem@davemloft.net> (raw)
In-Reply-To: <200608241516.34448.ian.mcdonald@jandi.co.nz>
From: Ian McDonald <ian.mcdonald@jandi.co.nz>
Date: Thu, 24 Aug 2006 15:16:33 +1200
> Please find following a series of patches for DCCP.
>
> These have been tested against torvalds/linux-2.6.git and davem/net-2.6.19.git
>
> My opinion is that 1 and 2 can go straight into 2.6.18 as documentation
> changes only - Dave - are you able to do as Arnaldo is very busy at present.
>
> I would love 3, 4, 5 to go into 2.6.18 as these resolve long standing CCID3
> issues that have been in the DCCP tree since inception and have caught a
> number of people.
Ok, I'll toss 1-5 into 2.6.18
One thing I don't understand is this description from patch 5:
--------------------
This gives a theoretical speed of 71.9 Kbits/s. I measured across three
runs with this patch set and got 70.1 Kbits/s. Without this patchset the
average was 232 Kbits/s which means Linux can't be used for CCID3 research
properly.
--------------------
Decreasing the transfer rate is desirable? I read this as saying
this "fix" drops the transfer rate down from 232Kb/sec to
70.1Kb/sec. What's going on here?
next prev parent reply other threads:[~2006-08-27 2:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 3:16 [PATCH 0/7] [DCCP]: Fixes and enhancements Ian McDonald
2006-08-24 11:59 ` David Miller
2006-08-24 18:09 ` Ian McDonald
2006-08-25 13:19 ` Arnaldo Carvalho de Melo
2006-08-27 2:08 ` David Miller [this message]
2006-08-27 3:46 ` Ian McDonald
2006-08-27 4:45 ` David Miller
2006-08-27 4:57 ` Ian McDonald
2006-08-27 5:39 ` David Miller
2006-08-27 6:18 ` 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=20060826.190851.74747699.davem@davemloft.net \
--to=davem@davemloft.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