From: Rick Jones <rick.jones2@hp.com>
To: Predrag Hodoba <predrag.hodoba@gmail.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
David Miller <davem@davemloft.net>,
dagriego@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] NET: Add TCP connection abort IOCTL
Date: Fri, 30 Mar 2007 13:46:26 -0700 [thread overview]
Message-ID: <460D7722.8030403@hp.com> (raw)
In-Reply-To: <46d726f90703301209o1147385fx9151c10f95e16684@mail.gmail.com>
If the switchover from active to standby is "commanded" then there is
the opportunity to "tell" the applications on the server to close their
connections - either explicitly with some sort of defined interface, or
implicitly by killing the processes. Then the IP can be brought-up on
the standby and processes started/enabled/whatever and the clients can
establish their new connections. The ioctl here (at least if it is like
the tcp_discon options in HP-UX/Solaris) wouldn't be any better than
just killing the process in so far as what happens on the network - in
fact, it could be worse since the RST will not be retransmitted if lost,
but FINs would. So, the ioctl could still leave clients twisting in the
ether waiting for their application-level heartbeats to kick-in anyway.
Heck, depending on their heartbeat lengths, even the FIN stuff if lost
could leave them depending on their heartbeats.
If the switchover from active to standby is "uncommanded" it probably
means the primary went belly-up which means you don't have the
opportunity to make an ioctl call anyway, and you are back to the
heartbeats.
rick jones
next prev parent reply other threads:[~2007-03-30 20:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 21:47 [PATCH] NET: Add TCP connection abort IOCTL David Griego
2007-03-27 22:30 ` David Miller
2007-03-27 23:09 ` Mark Huth
2007-03-27 23:36 ` David Miller
2007-03-28 6:02 ` Eric Dumazet
2007-03-28 6:35 ` David Miller
2007-03-28 0:27 ` John Heffner
2007-03-28 0:34 ` John Heffner
2007-03-28 3:09 ` Herbert Xu
2007-03-28 1:52 ` David Miller
2007-03-28 0:04 ` Rick Jones
2007-03-29 14:56 ` Predrag Hodoba
2007-03-29 18:41 ` David Miller
2007-03-30 1:09 ` Stephen Hemminger
2007-03-30 15:10 ` Predrag Hodoba
2007-03-30 18:33 ` Stephen Hemminger
2007-03-30 19:09 ` Predrag Hodoba
2007-03-30 20:46 ` Rick Jones [this message]
2007-03-31 6:25 ` Predrag Hodoba
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=460D7722.8030403@hp.com \
--to=rick.jones2@hp.com \
--cc=dagriego@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=predrag.hodoba@gmail.com \
--cc=shemminger@linux-foundation.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).