Re: Exporting obscene amounts of data in rtnl_link_ops->fill_info()

2015-11-01 Thread Jason A. Donenfeld
Hi folks, Just a follow-up on this thread... The basic issue is that for a given net device, I want to export to userspace more data than what can fit in a netlink sk_buff. On first glance, using RTM_GETLINK with the ops->fill_info() hook seemed perfect. It provides a simple interface for my rtne

Re: Exporting obscene amounts of data in rtnl_link_ops->fill_info()

2015-08-20 Thread Jason A. Donenfeld
On Thu, Aug 20, 2015 at 7:59 AM, Scott Feldman wrote: > > What kind of data are you sending up? Maybe there is an alternate interface. This is what I'm wondering about: alternative interfaces, that are still kosher in the netlink/rtnl world. Each interface is associated with a certain set of "pe

Re: Exporting obscene amounts of data in rtnl_link_ops->fill_info()

2015-08-19 Thread Scott Feldman
On Wed, Aug 19, 2015 at 5:47 PM, Jason A. Donenfeld wrote: > Hi guys, > > I have a new link driver that registers a rtnl_link_ops. For many > things, the rtnl interfaces are perfectly suited: I can use netlink in > userspace to check out packet counts, adjust interface parameters, and > all sorts