netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net, jiri@resnulli.us
Cc: netdev@vger.kernel.org, kernel-team@fb.com,
	jacob.e.keller@intel.com, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next v4 0/3] devlink: kernel region snapshot id allocation
Date: Fri,  1 May 2020 09:40:39 -0700	[thread overview]
Message-ID: <20200501164042.1430604-1-kuba@kernel.org> (raw)

Hi!

currently users have to find a free snapshot id to pass
to the kernel when they are requesting a snapshot to be
taken.

This set extends the kernel so it can allocate the id
on its own and send it back to user space in a response.

Jakub Kicinski (3):
  devlink: factor out building a snapshot notification
  devlink: let kernel allocate region snapshot id
  docs: devlink: clarify the scope of snapshot id

 .../networking/devlink/devlink-region.rst     | 11 ++-
 net/core/devlink.c                            | 96 ++++++++++++++-----
 .../drivers/net/netdevsim/devlink.sh          | 13 +++
 3 files changed, 94 insertions(+), 26 deletions(-)

-- 
2.25.4


             reply	other threads:[~2020-05-01 16:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 16:40 Jakub Kicinski [this message]
2020-05-01 16:40 ` [PATCH net-next v4 1/3] devlink: factor out building a snapshot notification Jakub Kicinski
2020-05-01 21:35   ` Jacob Keller
2020-05-01 16:40 ` [PATCH net-next v4 2/3] devlink: let kernel allocate region snapshot id Jakub Kicinski
2020-05-01 21:36   ` Jacob Keller
2020-05-01 16:40 ` [PATCH net-next v4 3/3] docs: devlink: clarify the scope of " Jakub Kicinski
2020-05-04 18:58 ` [PATCH net-next v4 0/3] devlink: kernel region snapshot id allocation David Miller

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=20200501164042.1430604-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jacob.e.keller@intel.com \
    --cc=jiri@resnulli.us \
    --cc=kernel-team@fb.com \
    --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).