kernel/linux.git/tools/testing/selftests/net/forwarding/README, branch v6.19.11Linux kernel stable tree (mirror)https://git.radix-linux.su/kernel/linux.git/atom?h=v6.19.112025-09-27T00:48:41+00:00selftests: forwarding: README: Mention defer, adf_2025-09-27T00:48:41+00:00Petr Machatapetrm@nvidia.com2025-09-25T17:31:56+00:00urn:sha1:fca6ff9191bd60167d5fe1d1fea89bf988d9e355
Mention how it would be nice if new code used defer. Also if it does that
in dirtying helpers, how it would be nice if these were named adf_*.
Signed-off-by: Petr Machata <petrm@nvidia.com>
Reviewed-by: Simon Horman <horms@kernel.org>
Link: https://patch.msgid.link/0764bdb9266cd516da23ddeec110e01118cf981e.1758821127.git.petrm@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
net: rename netns_local to netns_immutable2025-03-04T11:44:48+00:00Nicolas Dichtelnicolas.dichtel@6wind.com2025-02-28T10:20:56+00:00urn:sha1:0c493da86374dffff7505e67289ad75b21f5b301
The name 'netns_local' is confusing. A following commit will export it via
netlink, so let's use a more explicit name.
Reported-by: Eric Dumazet <edumazet@google.com>
Suggested-by: Kuniyuki Iwashima <kuniyu@amazon.com>
Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
netdev_features: convert NETIF_F_NETNS_LOCAL to dev->netns_local2024-09-03T09:36:43+00:00Alexander Lobakinaleksander.lobakin@intel.com2024-08-29T12:33:38+00:00urn:sha1:05c1280a2bcfca187fe7fa90bb240602cf54af0a
"Interface can't change network namespaces" is rather an attribute,
not a feature, and it can't be changed via Ethtool.
Make it a "cold" private flag instead of a netdev_feature and free
one more bit.
Signed-off-by: Alexander Lobakin <aleksander.lobakin@intel.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
selftests: forwarding: README: Document customization2024-03-29T01:03:42+00:00Petr Machatapetrm@nvidia.com2024-03-26T16:54:30+00:00urn:sha1:0cb862871fe7d338e0cf5229f0399d5c1630b8d0
That any sort of customization is possible at all, let alone how it should
be done, is currently not at all clear. Document the whats and hows in
README.
Signed-off-by: Petr Machata <petrm@nvidia.com>
Reviewed-by: Benjamin Poirier <bpoirier@nvidia.com>
Link: https://lore.kernel.org/r/e819623af6aaeea49e9dc36cecd95694fad73bb8.1711464583.git.petrm@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
selftests: forwarding: README: Require diagrams2018-06-27T01:42:13+00:00Petr Machatapetrm@mellanox.com2018-06-26T00:08:17+00:00urn:sha1:18ec44f6effbd7bd6f7ec95e8ccd324b05219224
ASCII art diagrams are well suited for presenting the topology that a
test uses while being easy to embed directly in the test file iteslf.
They make the information very easy to grasp even for simple topologies,
and for more complex ones they are almost essential, as figuring out the
interconnects from the script itself proves to be difficult.
Therefore state the requirement for topology ASCII art in README.
Signed-off-by: Petr Machata <petrm@mellanox.com>
Reviewed-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
selftests: forwarding: Add initial testing framework2018-02-28T17:25:47+00:00Ido Schimmelidosch@mellanox.com2018-02-28T10:25:06+00:00urn:sha1:73bae6736b6b577b52fbba2d4b71a5a3e9920fb5
Add initial framework to test packet forwarding functionality. The tests
can run on actual devices using loop-backed cables or using veth pairs.
Signed-off-by: Jiri Pirko <jiri@mellanox.com>
Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>