From: Andrew Lunn <andrew@lunn.ch>
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, netdev <netdev@vger.kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next 4/5] tsnep: Add TSN endpoint Ethernet MAC driver
Date: Wed, 28 Jul 2021 00:41:07 +0200 [thread overview]
Message-ID: <YQCLg3iLubJW+3yB@lunn.ch> (raw)
In-Reply-To: <CANr-f5y7eVbAf_NK3puJa3AcnkLXMbhzfwwmZ+r2KuWMbDhhsA@mail.gmail.com>
> I also expect some discussion about this feature. Mapping device specific
> TX/RX queues to user space is not done in mainline Linux so far.
That is probably not quite true. I expect GPUs do it, or at least
something very similar.
> I will follow your suggestion and drop tsnep_stream.c for the moment.
> Any early comments about this feature are welcome, because the direct
> use of additional TX/RX queues for real-time communication is the main
> feature of this device.
I know enough to know i don't know enough about cache management from
user space to be able to make any sensible recommendations.
You probably want to start a discussion with the XDP people and get
them to agree XDP does not work for your use case. Also, the people
who implemented zero-copy, MSG_ZEROCOPY and make sure that is also
unsuitable. Then see if you can reuse some GPU code which has been
well reviewed and tested. You will get less pushback that way,
compared to your own code which will need a good review by somebody
who understands all the issues.
Andrew
next prev parent reply other threads:[~2021-07-27 22:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 19:45 [PATCH net-next 0/5] TSN endpoint Ethernet MAC driver Gerhard Engleder
2021-07-26 19:45 ` [PATCH net-next 1/5] dt-bindings: Add vendor prefix for Engleder Gerhard Engleder
2021-07-26 19:46 ` [PATCH net-next 2/5] dt-bindings: net: Add tsnep Ethernet controller Gerhard Engleder
2021-07-26 23:35 ` Rob Herring
2021-07-27 18:34 ` Gerhard Engleder
2021-07-27 20:25 ` Rob Herring
2021-07-27 20:33 ` Gerhard Engleder
2021-07-28 5:13 ` Michal Simek
2021-07-28 7:44 ` Gerhard Engleder
2021-07-28 10:55 ` Michal Simek
2021-07-28 20:14 ` Gerhard Engleder
2021-07-29 5:07 ` Michal Simek
2021-07-29 7:07 ` Gerhard Engleder
2021-07-29 7:57 ` Michal Simek
2021-07-26 19:46 ` [PATCH net-next 3/5] dt-bindings: arm: Add Engleder bindings Gerhard Engleder
2021-07-26 19:46 ` [PATCH net-next 4/5] tsnep: Add TSN endpoint Ethernet MAC driver Gerhard Engleder
2021-07-26 20:49 ` Andrew Lunn
2021-07-27 20:18 ` Gerhard Engleder
2021-07-26 21:15 ` Andrew Lunn
2021-07-27 20:49 ` Gerhard Engleder
2021-07-26 21:29 ` Andrew Lunn
2021-07-27 22:05 ` Gerhard Engleder
2021-07-27 22:41 ` Andrew Lunn [this message]
2021-07-28 8:24 ` Gerhard Engleder
2021-07-26 23:25 ` kernel test robot
2021-07-26 23:25 ` kernel test robot
2021-07-26 19:46 ` [PATCH net-next 5/5] arm64: dts: zynqmp: Add ZCU104 based TSN endpoint Gerhard Engleder
2021-07-26 23:40 ` Rob Herring
2021-07-27 20:10 ` Gerhard Engleder
2021-07-27 20:17 ` Rob Herring
2021-07-27 20:23 ` Gerhard Engleder
2021-07-28 5:10 ` Michal Simek
2021-07-28 8:19 ` Gerhard Engleder
2021-07-28 10:58 ` Michal Simek
2021-07-28 20:51 ` Gerhard Engleder
2021-07-29 5:22 ` Michal Simek
2021-07-29 6:47 ` Gerhard Engleder
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=YQCLg3iLubJW+3yB@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gerhard@engleder-embedded.com \
--cc=kuba@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.