linux-kernel - Re: Chronic resource starvation.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 14 Jan 2012 14:21:12 -0600
From:	Mike Mestnik <cheako@...emestnik.net>
To:	linux-kernel@...r.kernel.org
Subject: Re: Chronic resource starvation.

On 01/13/12 21:17, Mike Mestnik wrote:
> I've dealt with applications taking extended time off for a number of
> years.  I typically attribute it to applications being overly zealous
> about eating memory as most every application tends to do these days.  I
> had always figured that there a likely plenty of ppl complaining and I
> didn't want to get the boiler plat answer that resources are cheap.
>
> I refuse to buy into the idea that Z computers can get an additional Y
> resource to run application X, when instead application X could be
> engineered once and for all.  This ideology is not sustainable and
> eventually will crash upon it's self.  I call this Z * Y < X.  The
> application source becomes the single location where every computers
> resources can be increased at the cost of much less then to adjust the
> running environment of every location that the code may run.
>
> Here is a 84MB video that demonstrates the issue.
> http://j.mp/wavbCO
> http://bitly.com/wavbCO+
I'm glad to see a number of you have clicked on this link.

Does this behavior look normal or is it just my system?  If it is normal
how difficult would it be to make corrections and would those
corrections likely be kernel or application related?
> You can see at the start an application that should update regularly is
> frozen and that moving windows and even focus is difficult.  The system
> does recover, but after far too long.
>
> I'll welcome any further testing as I'm sure it's needed.  Keep in mind
> that I can't reproduce this reliably, but it does happen, so it will
> take time to collect any amount of data...  A gkrellm plugin that
> illustrates the test is the most perfered, killing two birds with one
> stone as it will help with this case and many many future cases.  If
> it's important wouldn't your test already be part of a tool like gkrellm?
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/