netdev - long-lived tcp connection question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKA=qzaPwx53ExK7VhNC_sbv3tVZrnWXv-5Fh8akcZ6DEaqd9Q@mail.gmail.com>
Date:	Thu, 22 Mar 2012 11:56:19 -0500
From:	Josh Hunt <joshhunt00@...il.com>
To:	netdev@...r.kernel.org
Subject: long-lived tcp connection question

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.

Thanks
Josh
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html