From: Jakub Kicinski <kuba@kernel•org>
To: Jeremy Kerr <jk@codeconstruct•com.au>
Cc: Jian Zhang <zhangjian.3032@bytedance•com>,
netdev@vger•kernel.org, openbmc@lists•ozlabs.org,
Matt Johnston <matt@codeconstruct•com.au>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>,
open list <linux-kernel@vger•kernel.org>
Subject: Re: [PATCH net-next] mctp i2c: notify user space on TX failure
Date: Wed, 13 Nov 2024 19:19:09 -0800 [thread overview]
Message-ID: <20241113191909.10cf495e@kernel.org> (raw)
In-Reply-To: <da9b94909dcda3f0f7e48865e63d118c3be09a8d.camel@codeconstruct.com.au>
On Thu, 14 Nov 2024 11:13:33 +0800 Jeremy Kerr wrote:
> > notifying socket in the xmit handler of a netdev is a bit strange,
> > could you do it somewhere higher in the MCTP stack?
>
> Sounds like that would be useful in general for MCTP, but we don't have
> a facility for that at present. Any existing implementation you would
> suggest modelling this on?
routing isn't really my forte, TBH, what eats the error so that it
doesn't come out of mctp_local_output() ? Do you use qdiscs on top
of the MCTP devices?
next prev parent reply other threads:[~2024-11-14 3:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 9:42 [PATCH net-next] mctp i2c: notify user space on TX failure Jian Zhang
2024-11-14 3:09 ` Jakub Kicinski
2024-11-14 3:13 ` Jeremy Kerr
2024-11-14 3:19 ` Jakub Kicinski [this message]
2024-11-14 6:48 ` Jeremy Kerr
2024-11-14 15:02 ` Jakub Kicinski
2024-11-15 8:30 ` Marc Kleine-Budde
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=20241113191909.10cf495e@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=jk@codeconstruct$(echo .)com.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=matt@codeconstruct$(echo .)com.au \
--cc=netdev@vger$(echo .)kernel.org \
--cc=openbmc@lists$(echo .)ozlabs.org \
--cc=pabeni@redhat$(echo .)com \
--cc=zhangjian.3032@bytedance$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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