From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Josh Hunt <joshhunt00@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: long-lived tcp connection question
Date: Thu, 22 Mar 2012 22:51:50 +0100 [thread overview]
Message-ID: <20120322215150.GB3093@nuttenaction> (raw)
In-Reply-To: <CAKA=qzaPwx53ExK7VhNC_sbv3tVZrnWXv-5Fh8akcZ6DEaqd9Q@mail.gmail.com>
* Josh Hunt | 2012-03-22 11:56:19 [-0500]:
>Given things like web sockets with presumably long-lived persistent
>tcp connections and a sparse amount of data, I was wondering if there
>are currently any mechanisms in the kernel or out of tree projects
>which work on reducing the overhead these connections require?
>Possibly storing their state after a certain period of inactivity and
>then reviving them when work needs to be done? I'm thinking something
>along the lines of the state info stored for time-wait sockets and
>then the ability to resurrect it on an incoming packet. Keeping
>resources around for such connections seems inefficient although
>possibly unavoidable.
Do you referring to something like this:
https://datatracker.ietf.org/doc/draft-ietf-tcpm-fastopen/
The Linux code is not released yet, but I know that the required storage
overhead is small. Search the IETF email archive for more background
information about the topic.
Hagen
next prev parent reply other threads:[~2012-03-22 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 16:56 long-lived tcp connection question Josh Hunt
2012-03-22 21:51 ` Hagen Paul Pfeifer [this message]
2012-03-22 22:27 ` Josh Hunt
2012-03-22 22:29 ` Eric Dumazet
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=20120322215150.GB3093@nuttenaction \
--to=hagen@jauu.net \
--cc=joshhunt00@gmail.com \
--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).