From: chrubis@suse.cz
To: DAN LI <li.dan@cn.fujitsu.com>
Cc: LTP list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH v4] pthread_cond_brodcast/1-2.c hung when mem left is not enough
Date: Wed, 17 Oct 2012 12:09:02 +0200 [thread overview]
Message-ID: <20121017100902.GB26815@rei.Home> (raw)
In-Reply-To: <5077DDA1.1000206@cn.fujitsu.com>
Hi!
> > And actually I think that free ram itself is enough to figoure out
> > available memory as the kernel tends to eat as many memory for buffers
> > as available and reclaims it back only when needed.
> >
>
> Unfortunately i'v not got other good ideas.
> Do you have any suggestion?
There are several ways how to fix this.
One is to assume usable ram as free + buffers/N where N > 1
Another is to assume usable ram from total amount of RAM as
(total - M)/N where M statically reserved size and N > 1.
The problem is to choose the constats carefully so that we excersize the
system enough but don't overload it.
After you figure out this part, the patch with sysinfo() in header in
include is fine.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-10-17 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 5:06 [LTP] [PATCH v4] pthread_cond_brodcast/1-2.c hung when mem left is not enough DAN LI
2012-08-23 1:35 ` Wanlong Gao
2012-10-03 13:06 ` chrubis
[not found] ` <5077DDA1.1000206@cn.fujitsu.com>
2012-10-17 10:09 ` chrubis [this message]
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=20121017100902.GB26815@rei.Home \
--to=chrubis@suse.cz \
--cc=li.dan@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
/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