All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Lorenzo Allegrucci <lenstra@tiscalinet.it>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@transmeta.com>,
	Andrea Arcangeli <andrea@suse.de>
Subject: Re: new OOM heuristic failure  (was: Re: VM: qsbench)
Date: Fri, 02 Nov 2001 00:35:23 +0100	[thread overview]
Message-ID: <200111012335.AAA29493@webserver.ithnet.com> (raw)
In-Reply-To: <3.0.6.32.20011101225943.01fee1b0@pop.tiscalinet.it>

> At 22.08 01/11/01 +0100, you wrote:                                 
> >> Well, your patch works but it hurts performance :(               
                                                                      
> >>                                                                  
> >> lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
                                                                      
> >> 71.500u 1.790s 2:29.18 49.1%    0+0k 0+0io 18498pf+0w            
                                                                      
> >> lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
                                                                      
> >> 71.460u 1.990s 2:26.87 50.0%    0+0k 0+0io 18257pf+0w            
                                                                      
> >> lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
                                                                      
> >> 71.220u 2.200s 2:26.82 50.0%    0+0k 0+0io 18326pf+0w            
                                                                      
> >> 0:55 kswapd                                                      
                                                                      
> >>                                                                  
                                                                      
> >> Linux-2.4.14-pre5:                                               
                                                                      
> >> lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
                                                                      
> >> 70.340u 3.450s 2:13.62 55.2%    0+0k 0+0io 16829pf+0w            
                                                                      
> >> lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
                                                                      
> >> 70.590u 2.940s 2:15.48 54.2%    0+0k 0+0io 17182pf+0w            
                                                                      
> >> lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
                                                                      
> >> 70.140u 3.480s 2:14.66 54.6%    0+0k 0+0io 17122pf+0w            
                                                                      
> >> 0:01 kswapd                                                      
                                                                      
> >                                                                   
                                                                      
> >Hello Lorenzo,                                                     
                                                                      
> >                                                                   
                                                                      
> >to be honest: I expected that. The patch according to my knowledge 
                                                                      
> >fixes a "definition hole" in the shrink_cache algorithm. I tend to 
say                                                                   
> >it is the right thing to do it this way, but I am sure it is not as
                                                                      
> >fast as immediate exit to swap. It would be interesting to know if 
it                                                                    
> >does hurt performance in not-near-oom environment. I'd say Andrea  
or                                                                    
> >Linus might know that, or you can try, of course :-)               
                                                                      
To clarify this one a bit:                                            
shrink_cache is thought to do what it says, it is given a number of   
pages it should somehow manage to free by shrinking the cache. What my
patch does is go after the _whole_ list to fulfill that. One cannot   
really say that this is the wrong thing to do, I guess. If it takes   
time to _find_ free pages with shrink_cache, then probably the idea to
use it was wrong in the first place (which is not the fault of the    
function itself). Or the number of free-pages to find is to high, or  
(as a last but guess unrealistic approach) the swap_out eats the time 
and shouldn't be called when nr_pages (return value) is equal to zero.
This last one could be checked (hint hint Lorenzo ;-) by simply       
modifiying                                                            
                                                                      
if (max_swapped==0)                                                   
                                                                      
to                                                                    
                                                                      
if (max_swapped==0 && nr_pages>0)                                     
                                                                      
at the end of shrink_cache.                                           
Thinking again about this it really sounds like the right choice,     
because there is no need to swap when we fulfilled the requested      
number of free-pages.                                                 
                                                                      
You should try.                                                       
                                                                      
Thank you for your patience Lorenzo                                   
                                                                      
Regards,                                                              
Stephan                                                               
                                                                      
PS: just fishing for lobster, Linus ;-)                               
                                                                      
                                                                      

  reply	other threads:[~2001-11-01 23:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200111012108.WAA28044@webserver.ithnet.com>
     [not found] ` <3.0.6.32.20011101214957.01feaa70@pop.tiscalinet.it>
2001-11-01 21:59   ` new OOM heuristic failure (was: Re: VM: qsbench) Lorenzo Allegrucci
2001-11-01 23:35     ` Stephan von Krawczynski [this message]
2001-11-02  0:37       ` Linus Torvalds
2001-11-02  2:17         ` Stephan von Krawczynski
2001-11-02  2:21           ` Linus Torvalds
2001-11-02  2:30         ` Stephan von Krawczynski
2001-11-02  2:55           ` Stephan von Krawczynski
2001-11-02  2:37 Ed Tomlinson
2001-11-02  3:01 ` Stephan von Krawczynski
     [not found] <Pine.LNX.3.96.1011031133645.448B-100000@gollum.norang.ca>
2001-10-31 19:46 ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2001-10-31 12:12 VM: qsbench Lorenzo Allegrucci
2001-10-31 15:00 ` new OOM heuristic failure (was: Re: VM: qsbench) Rik van Riel
2001-10-31 15:52   ` Linus Torvalds
2001-10-31 16:04     ` Rik van Riel
2001-10-31 17:42       ` Stephan von Krawczynski
2001-10-31 18:22         ` Linus Torvalds
2001-10-31 17:55   ` Lorenzo Allegrucci
2001-10-31 18:06     ` Linus Torvalds
2001-10-31 21:31     ` Lorenzo Allegrucci
2001-11-02 13:00     ` Stephan von Krawczynski
2001-11-02 17:36     ` Lorenzo Allegrucci

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=200111012335.AAA29493@webserver.ithnet.com \
    --to=skraw@ithnet.com \
    --cc=andrea@suse.de \
    --cc=lenstra@tiscalinet.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.