Hi mentors,
I've gone through the xiphid.c file again and finally understood that part,After reading through your suggestions.
I've made a rough pen and paper documentation of my understanding of that file,which would get me through that file for future uses.
Although I understood addneigh | delneigh |showneighs and in xiphid.c , I dont see how it works overall .Shouuld a thorough read of this link make it better?
It’d be great if you give me a brief descriiption of neighbouring subsystems.
Also,that i have finished your initial recommendations of "first reading upon rtnl msgs and then try going through some principal's xip file like xiphid.c inside xip and then working your way up the directory.”,what should be my next course of action?
Please help me get a better understanding of the problem statement?
"For the xiart functions, can you provide me some examples of where the functions have been duplicated inside the principal files?"
Xiart functions are
1. xrt_modify_route /Based on iproute2/ip/iproute.c:iproute_modify. /
is fairly similar with modify_local (in xipether.c and xipu4id.c)
modify_addr(in xip hid.c)
modify_neigh(in xiphid.c and xipether.c)
defining a filter for the routing table dump and the dump function itself is pretty common in the codebase,with some minor variations.
2. static int dump(__u32 tbl_id, xid_type_t ty, rtnl_filter_t print)
is fairly similar with static int showaddrs(void) (in xiphid.c) [with a minor change in do_showaddrs we can use a common dump function maybe]
and similar with static int dump(void) (in xipu4id.c)
and static int dump(__u32 tbl_id, xid_type_t ty, rtnl_filter_t print) (in xipserval)
and static int dump(__u32 tbl_id, rtnl_filter_t print) (in xipxdp)
3. static int print_route(const struct sockaddr_nl *who, struct nlmsghdr *n,void *arg)
is duplicated in xipad.c and has some similarity with the print_route in xipu4id
print_addr in xiphid.c also shares a similar structure
static int
print_socket(const struct sockaddr_nl *who, struct nlmsghdr *n.void
*arg) in xipxdp,xipserval also shares a similar structure, With
minor changes we might implement a general one for all these xip
files.
I am attaching some of the differences/similarities in comparisons
--
You received this message because you are subscribed to the Google Groups "Linux XIA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-xia+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Linux XIA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-xia+unsubscribe@googlegroups.com.
The param_values argument is a string containing specifications of the values for module parameter which the kernel parses and initializes the specified parameters.
Can you validate the above and give me suggestions?
anything at all would be helpful
Thank you,much appreciated.I will do that. The formality apart,did that proposal seem to have realistic chances?