https://bugzilla.novell.com/show_bug.cgi?id=740631
https://bugzilla.novell.com/show_bug.cgi?id=740631#c10
--- Comment #10 from Scott Couston 2012-01-31 19:10:04 UTC ---
Created an attachment (id=473592)
--> (http://bugzilla.novell.com/attachment.cgi?id=473592)
1 of 5 in correct time line order
I am happy to leave this bug closed but I'm going to add some thoughts that
might just help later on.
My issue is the DYNAMIC use and allocation of cache buffers. After a DVD is
inserted with many files the cache buffers are allocated to use almost 90% of
base RAM.
If the same PC is left alone the cache buffers remain and the dynamic
allocation of the ceases to function.
After 90% of the total system RAM is allocated to cache buffers and considering
they are not dynamically flushed even after 3 days has gone by there IS a
problem.
In the following example the PC has 4GB of RAM and I have an application
running that has the kernel dynamically allocates 90% of base RAM to cache
buffers.
When I go to use Yast NFS Client the windowing manager freezes because the
kernel has not dynamically removed enough RAM from cache buffers for the
application to complete.
In fact in this test condition with 90% of RAM being used for cache buffers,
many applications wont even launch due the lack of base RAM.
The dynamic removal or reallocation of RAM used as cache buffers is not
functioning. Some aspect of the kernel has changed where the exists NO dynamic
allocation of cache buffers, NO dynamically added flag setting some cache
buffers as dirty and no dynamically controlled flushing of the dirty cache
buffers and dynamically returned to base RAM for further applications to launch
and/or not freeze and not slow due to the 10% being base RAM so the PC doesn't
crawl and/or not complete its task and not even opening some large aps like
ooo.
For the record I don’t open kernel bugs unless I am absolutely sure of the
problem and the problem is 100% reproducible on my quad core X64 AMD PC.
I am not in the habit of creating work for the developers that entails log
audit logs to be analysed or in this case the kernel being changed and
recompiled. Dynamic allocation of RAM is a complex algorithm,
I know this but I am sure something in the current Kernel is stopping the
process of dynamic use of RAM and debugging this part is hugely time consuming
and not to be taken lightly - I still believe the bug still exists, so for
future posterity I'll leave it closed
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.