On Wed 19-10-16 09:46:58, Stefan Schimanski wrote: > The production use case at hand is that mqueues should be customizable via > sysctls in Docker containers in a Kubernetes cluster. This can only be > safely allowed to the users of the cluster (without the risk that they can > cause resource shortage on a node, influencing other users' containers) if > all resources they control are bounded, i.e. accounted for. THis is a valuable information and should be a part of the changelog IMHO. > On Tue, Oct 18, 2016 at 9:30 PM, Alexey Dobriyan <adobriyan@xxxxxxxxx> > wrote: > > > On Tue, Oct 18, 2016 at 08:26:19PM +0200, Michal Hocko wrote: > > > On Tue 18-10-16 11:54:35, Aristeu Rozanski wrote: > > > > When kmem accounting switched from account by default to only account > > if > > > > flagged by __GFP_ACCOUNT, IPC mqueue and messages was left out. > > > > > > I guess this was because ipv msgqueue shouldn't allow for memory > > > consumption runaways. The number of message queues and messages pending > > > in them is bounded and not a large amount of memory AFAIR. Anyway I do > > > not see anything unreasonable about accounting the memory to the caller. > > > > It should be accounted because receiver may not intentionally or > > unintentionally > > consume messages. > > -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
