"Denis V. Lunev" <den@xxxxx> writes: > Daniel Lezcano wrote: >> The objective we have is to remove the fl_net field from the struct flowi. >> >> In the previous patch, we make the network namespace to go up to the > dst_entry. >> This patch makes an example in how we can use the dst_entry/rtable combined > with >> a container_of to retrieve the network namespace when we have the flowi > parameter. >> >> One restriction is we should pass always a flowi parameter coming from a > struct >> dst_entry. > this is an obfuscation IMHO. You use rtable instead of flowi, so > - rtable obtain flowi meaning and keeps original meaning > - stack usage in increased > > So, for the case, I think it is better to have an additional parameter > on IP route output path. (There is a device on the input one). Sounds right, and for shared code as well. The only reason I used flowi in my proof of concept implementation is that it seemed to be a prebuilt structure for passing that kind of thing so I could save a bit of pain by extending what already existed. Eric _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers