From: Ketan Kulkarni <ketkulka@gmail.com>
To: William Allen Simpson <william.allen.simpson@gmail.com>
Cc: cerowrt developers <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] administrative questions
Date: Thu, 31 Jan 2013 08:33:53 +0530 [thread overview]
Message-ID: <CAD6NSj5jMt0Wuw_rv_9EYmLbpQT40XT88OJEfwtqks4ecCZa8w@mail.gmail.com> (raw)
In-Reply-To: <51094F04.7010602@gmail.com>
On Wed, Jan 30, 2013 at 10:19 PM, William Allen Simpson
<william.allen.simpson@gmail.com> wrote:
> On 1/29/13 11:24 PM, Ketan Kulkarni wrote:
>>
>> To add issues and do tracking, you need to register. Once registered,
>> I can provide you the required access.
>> If you have registered already, please let me know your login id so I
>> can grant access. I couldn't find you in the user's list.
>>
> Thought the mail login would be sufficient, but apparently not. Made
> DayDreamer today. Was able to get https running, although it's not
> default for login! (probably should fix that.)
>
Thanks William. Please try re-logging in and you should get the required access.
>
>
>> Downloading the archives is a problem for everyone which I think
>> Dave(?) needs to address.
>>
> OK, I still use POP3 and Thunderbird, so I can grep and organize.
> None of that "cloud" stuff for me! :-)
>
>
>
>> You can submit the patches to this list, ccing Dave, or you can attach
>> it to the reported bugs for better future tracking.
>> All standard linux formatting applies here as well.
>>
> OK. I have various TCP, TCPCT (RFC 6013) and RFC1323bis patches from
> several years ago. I'm slowly updating my patches from 2.6.33 and .37
> to 3.7.4, but pretty much nothing is patching cleanly -- so it's going
> to be a long hard slog.
>
Yes there was a discussion about TCPCT recently on this list.
https://lists.bufferbloat.net/pipermail/cerowrt-devel/2013-January/000887.html
I also note the latest cero 3.7.2+ has the TCP Fast Open support. We
also have hacked few tools (httping and polipo proxy notably) to
support TCP Fast Open. The gains over wifi by TFO are pretty good.
Preliminary results here -
http://www.bufferbloat.net/attachments/158/multiple_packet_sizes.ods
Though I personally haven't looked at the security aspect of TFO, it
would be good to have wider views on the same. At the same time around
Dave pointed me to TCPCT RFC.
Thanks,
Ketan
next prev parent reply other threads:[~2013-01-31 3:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 18:42 William Allen Simpson
2013-01-30 4:24 ` Ketan Kulkarni
2013-01-30 16:49 ` William Allen Simpson
2013-01-31 3:03 ` Ketan Kulkarni [this message]
2013-01-31 16:28 ` William Allen Simpson
2013-01-31 17:43 ` William Allen Simpson
2013-02-01 15:51 ` Ketan Kulkarni
2013-02-04 6:06 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD6NSj5jMt0Wuw_rv_9EYmLbpQT40XT88OJEfwtqks4ecCZa8w@mail.gmail.com \
--to=ketkulka@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=william.allen.simpson@gmail.com \
/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