All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Mitsuru Kariya <Mitsuru.Kariya@oss.nttdata.com>
Cc: qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Fabiano Rosas" <farosas@suse.de>,
	"Laurent Vivier" <lvivier@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>
Subject: Re: [PATCH 2/5] qemu-options: document keep-alive-count/idle/interval for -netdev stream
Date: Tue, 21 Jul 2026 15:06:54 +0200	[thread overview]
Message-ID: <87ldb4o5jl.fsf@pond.sub.org> (raw)
In-Reply-To: <20260720053333.2316643-1-Mitsuru.Kariya@oss.nttdata.com> (Mitsuru Kariya's message of "Mon, 20 Jul 2026 14:33:33 +0900")

Mitsuru Kariya <Mitsuru.Kariya@oss.nttdata.com> writes:

> Thank you for reviewing, and I'm sorry for the late reply.
>
> Markus Armbruster <armbru@redhat.com> writes:
>> You document these options only for -netdev stream.  They also work
>> for -netdev dgram, possibly more (didn't check).  Shouldn't we
>> document them every where they work?
>
> As you pointed out, options such as keep-alive* are accepted by -netdev
> dgram as well. However, since these options are TCP-specific, they have
> no effect on sockets created by -netdev dgram.
> In fact, while these options are applied to sockets in
> inet_set_sockopts(), it is only called from inet_connect_saddr() and
> inet_listen_saddr(), which are for TCP, and not from inet_dgram_saddr(),
> which is for UDP. (I also confirmed this with strace.)
>
> Since the options are effectively no-ops there, I thought documenting
> them was unnecessary — but would you prefer that I add some note about
> it?

We should not accept options and then silently ignore them.

Can we reject them instead?

> For completeness, I also checked places other than -netdev stream and
> -incoming tcp:.
> For -blockdev driver=nbd and -drive driver=nbd, the keep-alive* options
> do take effect.  However, the documentation for -blockdev refers
> readers to the blockdev-add QMP command, and -drive is documented as
> accepting the same options as -blockdev, so I concluded that no
> additional description is needed there.
>
> As for -netdev socket, -drive file=nbd:, -chardev socket, and -vnc,
> they can also be used with TCP connections, but the keep-alive* options
> cannot be specified with them.

Thanks for checking!



  reply	other threads:[~2026-07-21 13:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-24  7:34 [PATCH 0/5] socket: add TCP_USER_TIMEOUT, fix -netdev stream option docs Mitsuru Kariya
2026-05-24  7:34 ` [PATCH 1/5] qemu-options: fix missing addr. prefix on -netdev stream inet/unix options Mitsuru Kariya
2026-06-02  4:33   ` Markus Armbruster
2026-05-24  7:34 ` [PATCH 2/5] qemu-options: document keep-alive-count/idle/interval for -netdev stream Mitsuru Kariya
2026-06-02  4:38   ` Markus Armbruster
2026-07-20  5:33     ` Mitsuru Kariya
2026-07-21 13:06       ` Markus Armbruster [this message]
2026-05-24  7:34 ` [PATCH 3/5] qemu-options: document keep-alive*/numeric/mptcp for -incoming tcp: Mitsuru Kariya
2026-05-24  7:34 ` [PATCH 4/5] util/qemu-sockets: add TCP_USER_TIMEOUT support Mitsuru Kariya
2026-06-02  4:54   ` Markus Armbruster
2026-07-20  5:33     ` Mitsuru Kariya
2026-07-21 13:12       ` Markus Armbruster
2026-05-24  7:34 ` [PATCH 5/5] tests/qtest/netdev-socket: smoke test -netdev stream inet option set Mitsuru Kariya

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=87ldb4o5jl.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=Mitsuru.Kariya@oss.nttdata.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=farosas@suse.de \
    --cc=jasowang@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=pierrick.bouvier@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.