Linux Container Development
 help / color / mirror / Atom feed
From: Pavel Labushev <p.labushev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Fwd: Re: lxc-performance?
Date: Fri, 15 Oct 2010 22:32:23 +0800	[thread overview]
Message-ID: <4CB865F7.8070904@gmail.com> (raw)
In-Reply-To: <4CB708A1.7000403-jI/kxupzh7HSLaPbPq81kw@public.gmane.org>

14.10.2010 21:41, MALATTAR пишет:

> also memtest command was able to allocate up to 1024MB but it takes a
> long time
> for one loop only ...

OK, the problem is not with LXC memory limits therefore.

> So, i think the problem is in my program not in the container, is not it?

It could be your program or too low rlimits. What 'ulimit -a' says? Note
that rlimits are per-process, so you should investigate their values
from inside your program's operating environment.

_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers

  parent reply	other threads:[~2010-10-15 14:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08  8:09 Fwd: Re: lxc-performance? MALATTAR
     [not found] ` <4CAED1CF.6050908-jI/kxupzh7HSLaPbPq81kw@public.gmane.org>
2010-10-08 16:41   ` Serge E. Hallyn
     [not found]     ` <20101008164122.GA16891-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
2010-10-11  8:05       ` MALATTAR
2010-10-12  5:05   ` KAMEZAWA Hiroyuki
     [not found]     ` <20101012140509.0ab6c617.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2010-10-14 13:41       ` MALATTAR
     [not found]         ` <4CB708A1.7000403-jI/kxupzh7HSLaPbPq81kw@public.gmane.org>
2010-10-14 13:54           ` Balbir Singh
2010-10-15 14:32           ` Pavel Labushev [this message]
2010-10-12 22:47   ` Serge E. Hallyn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CB865F7.8070904@gmail.com \
    --to=p.labushev-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox