On Wed, 14 Aug 2019 11:25:25 +0200 Martin Olsson <martin.olsson+net...@sentorsecurity.com> wrote:
> Hi Cong! > > Ah sorry. > Already implemented. Great! > > Hmmm. Then why don't the manual at > https://www.linux.org/docs/man8/tc-mirred.html to reflect the changes? > That was the place I checked to see if ingress was still not implemented. > In the commit you point at, the sentence "Currently only egress is > implemented" has been removed. The man pages on linux.org are not controlled by kernel/iproute developers. Not sure who builds/owns these and don't care. > Question: > Is there any form of performance penalty if I send the mirrored > traffic to the ingress queue of the destination interface rather than > to the egress queue? > I mean, in the kernel there is the possibility to perform far more > actions on the ingress queue than on the egress, but if I leave both > queues at their defaults, will mirrored packets to ingress use more > CPU cycles than to the egress destination, or are they more or less > identical? > > > Question 2: > Given the commit > https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=5eca0a3701223619a513c7209f7d9335ca1b4cfa, > how can I see in what kernel version it was added? Look at the tags $ git tag --contains 5eca0a3701223619a513c7209f7d9335ca1b4cfa v4.10.0 v4.11.0 v4.12.0 v4.13.0 v4.14.0 v4.14.1 v4.15.0 v4.16.0 v4.17.0 v4.18.0 v4.19.0 v4.20.0 v5.0.0 v5.1.0 v5.2.0 https://stackoverflow.com/questions/27886537/how-to-find-out-which-releases-contain-a-given-git-commit
