From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Kaike Wan <kaike.wan@intel.com>,
John Fleck <john.fleck@intel.com>,
Ira Weiny <ira.weiny@intel.com>, Thomas Graf <tgraf@suug.ch>,
Doug Ledford <dledford@redhat.com>,
Jiri Pirko <jiri@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: Netlink messages without NLM_F_REQUEST flag
Date: Wed, 7 Jun 2017 12:35:11 -0600 [thread overview]
Message-ID: <20170607183511.GA10225@obsidianresearch.com> (raw)
In-Reply-To: <20170607181810.GI1127@mtr-leonro.local>
On Wed, Jun 07, 2017 at 09:18:10PM +0300, Leon Romanovsky wrote:
> > AFAIK, that is different, that is acking and retriggering a single shot
> > notification, not completing a kernel initiated handshake.
>
> It is acking that message from user was received by kernel and now
> processing.
But isn't what is cared about here - the SA thing needs to send a
request to user space and collect a reply, it runs the protocol
backwards from normal.
It is not a notification because the request actually needs a reply,
and ACK's don't help because the reply has content.
It does not use the NOTIFICATION/REQUEST/REPLY sequence because it
does not care about reliability of delivering the REQUEST to user
space.
Jason
next prev parent reply other threads:[~2017-06-07 18:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 16:19 Netlink messages without NLM_F_REQUEST flag Leon Romanovsky
[not found] ` <20170607161901.GD1127-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-06-07 16:37 ` Jason Gunthorpe
[not found] ` <20170607163758.GA25313-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-06-07 16:43 ` Leon Romanovsky
[not found] ` <CALq1K=Jj_jJ5_OAiiws-es37tFEsLeLJeSvnU+bfwd0KLkGM3Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-07 16:47 ` Jason Gunthorpe
[not found] ` <20170607164750.GA7507-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-06-07 17:00 ` Leon Romanovsky
[not found] ` <20170607170037.GG1127-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-06-07 17:07 ` Jason Gunthorpe
[not found] ` <20170607170702.GB7507-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-06-07 18:18 ` Leon Romanovsky
[not found] ` <20170607181810.GI1127-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-06-07 18:26 ` Hefty, Sean
2017-06-07 18:35 ` Jason Gunthorpe [this message]
[not found] ` <20170607183511.GA10225-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-06-08 5:08 ` Leon Romanovsky
2017-06-07 17:10 ` Weiny, Ira
2017-06-07 18:13 ` Leon Romanovsky
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=20170607183511.GA10225@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=dledford@redhat.com \
--cc=ira.weiny@intel.com \
--cc=jiri@mellanox.com \
--cc=john.fleck@intel.com \
--cc=kaike.wan@intel.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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