Re: [PATCH v3 net-next 3/5] sock: ULP infrastructure

2017-08-08 Thread Tom Herbert
On Tue, Aug 8, 2017 at 9:38 AM, Hannes Frederic Sowa wrote: > Tom Herbert writes: > >> +#ifdef CONFIG_MODULES >> + if (!ulp && capable(CAP_NET_ADMIN)) { >> + rcu_read_unlock(); >> + request_module("%s", name); >> +

Re: [PATCH v3 net-next 3/5] sock: ULP infrastructure

2017-08-08 Thread Hannes Frederic Sowa
Tom Herbert writes: > +#ifdef CONFIG_MODULES > + if (!ulp && capable(CAP_NET_ADMIN)) { > + rcu_read_unlock(); > + request_module("%s", name); > + rcu_read_lock(); > + ulp = ulp_find(name); > + } > +#endif It looks to

Re: [PATCH v3 net-next 3/5] sock: ULP infrastructure

2017-08-08 Thread John Fastabend
On 08/07/2017 10:28 AM, Tom Herbert wrote: > Generalize the TCP ULP infrastructure recently introduced to support > kTLS. This adds a SO_ULP socket option and creates new fields in > sock structure for ULP ops and ULP data. Also, the interface allows > additional per ULP parameters to be set so

[PATCH v3 net-next 3/5] sock: ULP infrastructure

2017-08-07 Thread Tom Herbert
Generalize the TCP ULP infrastructure recently introduced to support kTLS. This adds a SO_ULP socket option and creates new fields in sock structure for ULP ops and ULP data. Also, the interface allows additional per ULP parameters to be set so that a ULP can be pushed and operations started in