Qiang Huang 15c93ee9e0 Revert "Use update time to detect if kmem limits have been set" ...

Revert: #935
Fixes: #946

I can reproduce #946 on some machines, the problem is on
some machines, it could be very fast that modify time
of `memory.kmem.limit_in_bytes` could be the same as
before it's modified.

And now we'll call `SetKernelMemory` twice on container
creation which cause the second time failure.

Revert this before we find a better solution.

Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>

2016-07-21 19:14:38 +08:00

..

linux.go

Fix trivial style errors reported by go vet and golint

2016-04-12 08:13:16 +00:00

proc.go

Move libcontainer into subdirectory

2015-06-21 19:29:15 -07:00

setns_linux.go

Move libcontainer into subdirectory

2015-06-21 19:29:15 -07:00

syscall_linux_64.go

Move libcontainer into subdirectory

2015-06-21 19:29:15 -07:00

syscall_linux_386.go

Fix build tags

2015-07-01 13:22:09 -07:00

syscall_linux_arm.go

Fix build tags

2015-07-01 13:22:09 -07:00

sysconfig_notcgo.go

Move libcontainer into subdirectory

2015-06-21 19:29:15 -07:00

sysconfig.go

Revert "Use update time to detect if kmem limits have been set"

2016-07-21 19:14:38 +08:00

unsupported.go

Stub RunningInUserNS for non-Linux

2016-03-03 16:33:43 -05:00

xattrs_linux.go

Move libcontainer into subdirectory

2015-06-21 19:29:15 -07:00