Re: [Devel] [PATCH] ve/fs: add per-VE limit of mount points

2015-11-09 Thread Stanislav Kinsburskiy
09.11.2015 15:13, Andrew Vagin пишет: On Thu, Nov 05, 2015 at 07:37:31PM +0300, Evgenii Shatokhin wrote: 05.11.2015 18:45, Konstantin Khorenko пишет: Zenya, 1) an idea from Volodya Davydov: we can store the pointer to ve_struct, not the veid, thus we'll eliminate possible races with

Re: [Devel] [PATCH] ve/fs: add per-VE limit of mount points

2015-11-09 Thread Andrew Vagin
On Thu, Nov 05, 2015 at 07:37:31PM +0300, Evgenii Shatokhin wrote: > 05.11.2015 18:45, Konstantin Khorenko пишет: > >Zenya, > > > >1) an idea from Volodya Davydov: we can store the pointer to ve_struct, > >not the veid, > >thus we'll eliminate possible races with veid reuse. > > OK. > The

Re: [Devel] [PATCH] ve/fs: add per-VE limit of mount points

2015-11-09 Thread Vladimir Davydov
On Mon, Nov 09, 2015 at 04:23:34PM +0100, Stanislav Kinsburskiу wrote: > > 9 нояб. 2015 г. 4:15 PM пользователь Vladimir Davydov > написал: > > > > On Mon, Nov 09, 2015 at 03:51:11PM +0100, Stanislav Kinsburskiy wrote: > > > > > > > > > 09.11.2015 15:13, Andrew Vagin

Re: [Devel] [PATCH] ve/fs: add per-VE limit of mount points

2015-11-09 Thread Stanislav Kinsburskiу
9 нояб. 2015 г. 4:31 PM пользователь Vladimir Davydov написал: > > On Mon, Nov 09, 2015 at 04:23:34PM +0100, Stanislav Kinsburskiу wrote: > > > > 9 нояб. 2015 г. 4:15 PM пользователь Vladimir Davydov > > написал: > > > > > > On Mon, Nov 09,

Re: [Devel] [PATCH] ve/fs: add per-VE limit of mount points

2015-11-09 Thread Stanislav Kinsburskiу
9 нояб. 2015 г. 4:15 PM пользователь Vladimir Davydov написал: > > On Mon, Nov 09, 2015 at 03:51:11PM +0100, Stanislav Kinsburskiy wrote: > > > > > > 09.11.2015 15:13, Andrew Vagin пишет: > > >On Thu, Nov 05, 2015 at 07:37:31PM +0300, Evgenii Shatokhin wrote: > >

Re: [Devel] [PATCH] ve/fs: add per-VE limit of mount points

2015-11-09 Thread Vladimir Davydov
On Mon, Nov 09, 2015 at 03:51:11PM +0100, Stanislav Kinsburskiy wrote: > > > 09.11.2015 15:13, Andrew Vagin пишет: > >On Thu, Nov 05, 2015 at 07:37:31PM +0300, Evgenii Shatokhin wrote: > >>05.11.2015 18:45, Konstantin Khorenko пишет: > >>>Zenya, > >>> > >>>1) an idea from Volodya Davydov: we can

Re: [Devel] [PATCH] ve/fs: add per-VE limit of mount points

2015-11-05 Thread Evgenii Shatokhin
05.11.2015 18:45, Konstantin Khorenko пишет: Zenya, 1) an idea from Volodya Davydov: we can store the pointer to ve_struct, not the veid, thus we'll eliminate possible races with veid reuse. OK. The main question is though, whether we should care about the situations where something is

Re: [Devel] [PATCH] ve/fs: add per-VE limit of mount points

2015-11-05 Thread Konstantin Khorenko
Zenya, 1) an idea from Volodya Davydov: we can store the pointer to ve_struct, not the veid, thus we'll eliminate possible races with veid reuse. 2) there are 2 more comments from Stas (3 total), please take a look. i don't mind leaving it as a global sysctl because hopefully it will

Re: [Devel] [PATCH] ve/fs: add per-VE limit of mount points

2015-11-04 Thread Evgenii Shatokhin
02.11.2015 18:47, Stanislav Kinsburskiy пишет: Yet again these sysctl handles...((( I have some questions. Please, see inlined. 02.11.2015 16:11, Evgenii Shatokhin пишет: https://jira.sw.ru/browse/PSBM-34438 (This fix was adapted from PCS6.) It is possible for a container to create lots of

Re: [Devel] [PATCH] ve/fs: add per-VE limit of mount points

2015-11-02 Thread Stanislav Kinsburskiy
Yet again these sysctl handles...((( I have some questions. Please, see inlined. 02.11.2015 16:11, Evgenii Shatokhin пишет: https://jira.sw.ru/browse/PSBM-34438 (This fix was adapted from PCS6.) It is possible for a container to create lots of mount points, which may make operations with them

[Devel] [PATCH] ve/fs: add per-VE limit of mount points

2015-11-02 Thread Evgenii Shatokhin
https://jira.sw.ru/browse/PSBM-34438 (This fix was adapted from PCS6.) It is possible for a container to create lots of mount points, which may make operations with them slower. As some of these operations take global locks (namespace_sem, vfsmount_lock), it might affect other containers as