From: David Miller <davem@davemloft.net>
To: dhowells@redhat.com
Cc: netdev@vger.kernel.org, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] rxrpc: Add bits for kernel services
Date: Fri, 20 Oct 2017 08:43:08 +0100 (WEST) [thread overview]
Message-ID: <20171020.084308.2182191337868415716.davem@davemloft.net> (raw)
In-Reply-To: <150832775000.7695.7720685597577836060.stgit@warthog.procyon.org.uk>
From: David Howells <dhowells@redhat.com>
Date: Wed, 18 Oct 2017 12:55:50 +0100
>
> Here are some patches that add a few things for kernel services to use:
>
> (1) Allow service upgrade to be requested and allow the resultant actual
> service ID to be obtained.
>
> (2) Allow the RTT time of a call to be obtained.
>
> (3) Allow a kernel service to find out if a call is still alive on a
> server between transmitting a request and getting the reply.
>
> (4) Allow data transmission to ignore signals if transmission progress is
> being made in reasonable time. This is also usable by userspace by
> passing MSG_WAITALL to sendmsg()[*].
>
> [*] I'm not sure this is the right interface for this or whether a sockopt
> should be used instead.
>
> The patches can be found here also:
>
> http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-next
>
> Tagged thusly:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> rxrpc-next-20171018
Pulled, thanks David.
prev parent reply other threads:[~2017-10-20 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 11:55 [PATCH net-next 0/3] rxrpc: Add bits for kernel services David Howells
2017-10-18 11:55 ` [PATCH net-next 1/3] rxrpc: Support service upgrade from a kernel service David Howells
2017-10-18 11:56 ` [PATCH net-next 2/3] rxrpc: Provide functions for allowing cleaner handling of signals David Howells
2017-10-18 11:56 ` [PATCH net-next 3/3] rxrpc: Use MSG_WAITALL to tell sendmsg() to temporarily ignore signals David Howells
2017-10-20 7:43 ` David Miller [this message]
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=20171020.084308.2182191337868415716.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).