From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: vsementsov@virtuozzo.com, berrange@redhat.com, armbru@redhat.com,
kraxel@redhat.com, den@openvz.org
Subject: [PATCH 0/2] keepalive default
Date: Wed, 8 Jul 2020 22:15:37 +0300 [thread overview]
Message-ID: <20200708191540.28455-1-vsementsov@virtuozzo.com> (raw)
Hi all!
We understood, that keepalive is almost superfluous with default 2 hours
in /proc/tcp_keepalive_time. Forcing user to setup keepalive for the
whole system doesn't seem right, better setup it per-socket.
These series suggests to set some defaults for keepalive settings as
well as set keepalive itself by default.
keepalive helps to not hang on io other side is down.
Vladimir Sementsov-Ogievskiy (2):
sockets: keep-alive settings
util/qemu-sockets: make keep-alive enabled by default
qapi/sockets.json | 33 +++++++++++++++++-
util/qemu-sockets.c | 81 +++++++++++++++++++++++++++++++++++++++------
2 files changed, 102 insertions(+), 12 deletions(-)
--
2.21.0
next reply other threads:[~2020-07-08 19:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 19:15 Vladimir Sementsov-Ogievskiy [this message]
2020-07-08 19:15 ` [PATCH 1/2] sockets: keep-alive settings Vladimir Sementsov-Ogievskiy
2020-07-09 8:33 ` Daniel P. Berrangé
2020-07-08 19:15 ` [PATCH 2/2] util/qemu-sockets: make keep-alive enabled by default Vladimir Sementsov-Ogievskiy
2020-07-09 8:29 ` Daniel P. Berrangé
2020-07-09 8:49 ` Vladimir Sementsov-Ogievskiy
2020-07-09 11:52 ` Daniel P. Berrangé
2020-07-09 8:54 ` Denis V. Lunev
2020-07-09 11:40 ` Markus Armbruster
2020-07-08 19:41 ` [PATCH 0/2] keepalive default no-reply
2020-07-09 8:35 ` Daniel P. Berrangé
2020-07-09 15:34 ` Eric Blake
2020-07-09 17:14 ` Vladimir Sementsov-Ogievskiy
2020-07-10 19:25 ` Vladimir Sementsov-Ogievskiy
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=20200708191540.28455-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=den@openvz.org \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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).