From: Jeremy Kerr <jk@codeconstruct.com.au>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Matt Johnston <matt@codeconstruct.com.au>,
Andrew Jeffery <andrew@aj.id.au>
Subject: [PATCH net-next v2 0/3] MCTP flow support
Date: Fri, 29 Oct 2021 11:01:42 +0800 [thread overview]
Message-ID: <20211029030145.633626-1-jk@codeconstruct.com.au> (raw)
For certain MCTP transport bindings, the binding driver will need to be
aware of request/response pairing. For example, the i2c binding may need
to set multiplexer configuration when expecting a response from a device
behind a mux.
This series implements a mechanism for informing the driver about these
flows, so it can implement transport-specific behaviour when a flow is
in progress (ie, a response is expected, and/or we time-out on that
expectation). We use a skb extension to notify the driver about the
presence of a flow, and a new dev->ops callback to notify about a flow's
destruction.
Cheers,
Jeremy
---
v2:
- add cover letter
- fix CONFIG combinations when MCTP_FLOWS=n
Jeremy Kerr (3):
mctp: Return new key from mctp_alloc_local_tag
mctp: Add flow extension to skb
mctp: Pass flow data & flow release events to drivers
include/linux/skbuff.h | 3 ++
include/net/mctp.h | 13 +++++++
include/net/mctpdevice.h | 16 ++++++++
net/core/skbuff.c | 19 +++++++++
net/mctp/Kconfig | 7 +++-
net/mctp/device.c | 51 ++++++++++++++++++++++++
net/mctp/route.c | 83 +++++++++++++++++++++++++++++++++-------
7 files changed, 177 insertions(+), 15 deletions(-)
--
2.33.0
next reply other threads:[~2021-10-29 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 3:01 Jeremy Kerr [this message]
2021-10-29 3:01 ` [PATCH net-next v2 1/3] mctp: Return new key from mctp_alloc_local_tag Jeremy Kerr
2021-10-29 3:01 ` [PATCH net-next v2 2/3] mctp: Add flow extension to skb Jeremy Kerr
2021-10-29 3:01 ` [PATCH net-next v2 3/3] mctp: Pass flow data & flow release events to drivers Jeremy Kerr
2021-10-29 12:40 ` [PATCH net-next v2 0/3] MCTP flow support patchwork-bot+netdevbpf
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=20211029030145.633626-1-jk@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=andrew@aj.id.au \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=matt@codeconstruct.com.au \
--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).