On 03/08/2018 10:11 AM, David Miller wrote:
Yeah, understood. At small scale the current behavior maybe made
sense, but these days it really doesn't.
No objections to the knob if you want to submit it.
Thanks David, I have rebased my patch and sent it.
New numbers on net-next are looking
From: Eric Dumazet
Date: Thu, 8 Mar 2018 10:05:12 -0800
> Another problematic legacy behavior is the automatic creation of
> fallback tunnels, which hurts netns creation/deletion.
>
> Some environments want to create a netns for every job/task, and they
> do not care if the init netns has these
On 03/08/2018 09:34 AM, David Miller wrote:
From: Stephen Hemminger
Date: Tue, 6 Mar 2018 15:59:20 -0800
Actually dev_load by ethernet name is really a legacy thing that
should just die,
It was kept around so that some very tunnel configuration using special names.
# ifconfig sit0
From: Stephen Hemminger
Date: Tue, 6 Mar 2018 15:59:20 -0800
> Actually dev_load by ethernet name is really a legacy thing that
> should just die,
>
> It was kept around so that some very tunnel configuration using special names.
>
> # ifconfig sit0
>
> which probably several web pages s
From: Paul Moore
Date: Tue, 6 Mar 2018 17:32:47 -0500
> On Tue, Mar 6, 2018 at 5:27 PM, Paul Moore wrote:
>> From: Paul Moore
>>
>> Starting with v4.16-rc1 we've been seeing a higher than usual number
>> of requests for the kernel to load networking modules, even on events
>> which shouldn't tr
On Tue, Mar 6, 2018 at 6:59 PM, Stephen Hemminger
wrote:
> On Tue, 06 Mar 2018 17:27:44 -0500
> Paul Moore wrote:
>> From: Paul Moore
>>
>> Starting with v4.16-rc1 we've been seeing a higher than usual number
>> of requests for the kernel to load networking modules, even on events
>> which shoul
On Tue, 06 Mar 2018 17:27:44 -0500
Paul Moore wrote:
> From: Paul Moore
>
> Starting with v4.16-rc1 we've been seeing a higher than usual number
> of requests for the kernel to load networking modules, even on events
> which shouldn't trigger a module load (e.g. ioctl(TCGETS)). Stephen
> Small
On Tue, Mar 6, 2018 at 5:27 PM, Paul Moore wrote:
> From: Paul Moore
>
> Starting with v4.16-rc1 we've been seeing a higher than usual number
> of requests for the kernel to load networking modules, even on events
> which shouldn't trigger a module load (e.g. ioctl(TCGETS)). Stephen
> Smalley su
From: Paul Moore
Starting with v4.16-rc1 we've been seeing a higher than usual number
of requests for the kernel to load networking modules, even on events
which shouldn't trigger a module load (e.g. ioctl(TCGETS)). Stephen
Smalley suggested the problem may lie in commit 44c02a2c3dc5
("dev_ioctl
