mbox series

[net-next,v2,0/3] MCTP flow support

Message ID 20211029030145.633626-1-jk@codeconstruct.com.au (mailing list archive)
Headers show
Series MCTP flow support | expand

Message

Jeremy Kerr Oct. 29, 2021, 3:01 a.m. UTC
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(-)

Comments

patchwork-bot+netdevbpf@kernel.org Oct. 29, 2021, 12:40 p.m. UTC | #1
Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri, 29 Oct 2021 11:01:42 +0800 you wrote:
> 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.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/3] mctp: Return new key from mctp_alloc_local_tag
    https://git.kernel.org/netdev/net-next/c/212c10c3c658
  - [net-next,v2,2/3] mctp: Add flow extension to skb
    https://git.kernel.org/netdev/net-next/c/78476d315e19
  - [net-next,v2,3/3] mctp: Pass flow data & flow release events to drivers
    https://git.kernel.org/netdev/net-next/c/67737c457281

You are awesome, thank you!