Duh, got it, thanks.
Hemant From: [email protected] <[email protected]> Sent: Sunday, October 04, 2020 7:20 AM To: [email protected]; [email protected] Subject: RE: [vpp-dev] ethernet-input vs. device-input? Search for VNET_FEATURE_ARC_INIT and answer your own question. Here's the declaration of the "device-input" arc, which explains why it's the right arc for use-cases which involve processing packets fresh from device drivers, prior to ethernet-input: VNET_FEATURE_ARC_INIT (device_input, static) = { .arc_name = "device-input", .start_nodes = VNET_FEATURES ("device-input"), .last_in_arc = "ethernet-input", .arc_index_ptr = &feature_main.device_input_feature_arc_index, }; From: [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]> > On Behalf Of hemant via lists.fd.io Sent: Saturday, October 3, 2020 7:00 PM To: [email protected] <mailto:[email protected]> Subject: [vpp-dev] ethernet-input vs. device-input? In vpp/src/plugin/, I see several instances of .arc_name = "device-input" being used. However, I don't since a single instance of .arc_name being "ethernet-input". Wonder why is that? Is ethernet-input not supposed to be used by a plugin? I was thinking I'd use ethernet-input rather than device-input. Thanks, Hemant
smime.p7s
Description: S/MIME cryptographic signature
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17640): https://lists.fd.io/g/vpp-dev/message/17640 Mute This Topic: https://lists.fd.io/mt/77290344/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
