Hello,
ks> Also can you please tell me what is dst_input() forloop meant for .
ks> Infact the code seems to match for dst_output() in terms of the
ks> NET_XMIT_BYPASS usage.
ks> Infact I saw that ip_rcv_finish() calls this dst_input() what purpose
ks> does it serve.
I assume most of the time or maybe always the for-loop reduces to a single
function call, either ip_forward or ip_local_deliver.
(see ip_route_input_slow, watch out for rth->u.dst.input = ...)
Maybe someone else can explain, if there are scenarios where more that
one dst input function comes into play or whether it was just done to
keep it analog to dst_output ...?
Best regards
Michael Becker
Hochschule Niederrhein - Krefeld, Germany
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
