netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: netdev@vger.kernel.org
Subject: Re: How I can reset TCP sockets after long suspend/resume cyscle
Date: Fri, 6 Jun 2008 00:19:17 +0300	[thread overview]
Message-ID: <200806060019.17589.maximlevitsky@gmail.com> (raw)
In-Reply-To: <20080605071339.GA11562@2ka.mipt.ru>

On Thursday, 5 June 2008 10:13:40 Evgeniy Polyakov wrote:
> On Sun, Jun 01, 2008 at 03:15:14PM +0300, Maxim Levitsky (maximlevitsky@gmail.com) wrote:
> > Is there a way to close all TCP sockets before/after suspend to ram?
> 
> You can do that with frevoke patchset (not in mainline though iirc),
> which allows you to close any file descriptor, which you can find via
> /proc/$pid/fd
> 

Seems like a great idea.
Do you know the status of this patchset, when to expect it to be
in included in mainline?


Thanks a lot,
	Best regards,
		Maxim Levitsky

  reply	other threads:[~2008-06-05 21:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01 12:15 How I can reset TCP sockets after long suspend/resume cyscle Maxim Levitsky
2008-06-04 15:34 ` Maxim Levitsky
2008-06-04 16:09   ` Adam Langley
2008-06-04 16:21     ` Stephen Hemminger
2008-06-04 21:00       ` Maxim Levitsky
2008-06-04 21:02       ` Rick Jones
2008-06-04 20:52     ` Maxim Levitsky
2008-06-04 21:15       ` Stephen Hemminger
2008-06-04 21:23         ` Rick Jones
2008-06-05 21:31           ` Maxim Levitsky
2008-06-05 21:50             ` Rick Jones
2008-06-06  8:37             ` Benny Amorsen
2008-06-06  9:27               ` Nadejda Levitsky
2008-06-05  7:13 ` Evgeniy Polyakov
2008-06-05 21:19   ` Maxim Levitsky [this message]
2008-06-05 22:20     ` Evgeniy Polyakov

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=200806060019.17589.maximlevitsky@gmail.com \
    --to=maximlevitsky@gmail.com \
    --cc=johnpol@2ka.mipt.ru \
    --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).