Re: [PATCH net-next 1/5] rhashtable: Don't reset walker table in rhashtable_walk_start

2017-12-01 Thread Tom Herbert
On Fri, Dec 1, 2017 at 3:29 PM, Tom Herbert wrote: > On Fri, Dec 1, 2017 at 2:18 PM, Herbert Xu > wrote: >> On Thu, Nov 30, 2017 at 04:03:01PM -0800, Tom Herbert wrote: >>> Remove the code that resets the walker table. The walker table should >>> only be initialized in the walk init function or

Re: [PATCH net-next 1/5] rhashtable: Don't reset walker table in rhashtable_walk_start

2017-12-01 Thread Tom Herbert
On Fri, Dec 1, 2017 at 2:18 PM, Herbert Xu wrote: > On Thu, Nov 30, 2017 at 04:03:01PM -0800, Tom Herbert wrote: >> Remove the code that resets the walker table. The walker table should >> only be initialized in the walk init function or when a future table is >> encountered. If the walker table i

Re: [PATCH net-next 1/5] rhashtable: Don't reset walker table in rhashtable_walk_start

2017-12-01 Thread Herbert Xu
On Thu, Nov 30, 2017 at 04:03:01PM -0800, Tom Herbert wrote: > Remove the code that resets the walker table. The walker table should > only be initialized in the walk init function or when a future table is > encountered. If the walker table is NULL this is the indication that > the walk has comple

[PATCH net-next 1/5] rhashtable: Don't reset walker table in rhashtable_walk_start

2017-11-30 Thread Tom Herbert
Remove the code that resets the walker table. The walker table should only be initialized in the walk init function or when a future table is encountered. If the walker table is NULL this is the indication that the walk has completed and this information can be used to break a multi-call walk in th