linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Puppetmaster <akhripin@mbhs.edu>
To: Timur Tabi <ttabi@interactivesi.com>
Cc: Linux MM mailing list <linux-mm@kvack.org>
Subject: Re: 2.4: why is NR_GFPINDEX so large?
Date: Wed, 21 Jun 2000 16:23:30 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10006211622270.10983-100000@binx.mbhs.edu> (raw)
In-Reply-To: <20000621200418Z131176-21004+46@kanga.kvack.org>

On Wed, 21 Jun 2000, Timur Tabi wrote:

> ** Reply to message from Kanoj Sarcar <kanoj@google.engr.sgi.com> on Wed, 21
> Jun 2000 12:56:12 -0700 (PDT)
> 
> 
> > This is a left over from the days when we had a few more __GFP_ flags,
> > but that has been cleaned up now, so NR_GFPINDEX can go down. 
> 
> Cool.  I'm glad to see that my questions wasn't stupid :-)
> 
> >Be aware 
> > of any cache footprint issues though.
> 
> Ok, you just lost me.  What's a "cache footprint"?
Cache footprint refers to the amount of space code/data take up in the
cache. This is important for code that is frequently executed, as it is
very good performance-wise to have the nescessary data and code entirely
in the L1 cache.
 > 
> 
> 
> 
> --
> Timur Tabi - ttabi@interactivesi.com
> Interactive Silicon - http://www.interactivesi.com
> 
> When replying to a mailing-list message, please don't cc: me, because then I'll just get two copies of the same message.
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org.  For more info on Linux MM,
> see: http://www.linux.eu.org/Linux-MM/
> 

-- 
Master! Master! Where's the dreams that I've been after?
           Master! Master! Promised only lies!         
  Laughter! Laughter! All I hear and see is laughter,
       Laughter! Laughter! Laughing at my cries!

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-06-21 20:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-21 19:48 Timur Tabi
2000-06-21 19:56 ` Kanoj Sarcar
2000-06-21 19:57   ` Timur Tabi
2000-06-21 20:23     ` Puppetmaster [this message]
2000-06-21 20:37       ` Timur Tabi
2000-06-21 20:37     ` Kanoj Sarcar
2000-06-21 20:41       ` Timur Tabi
2000-06-21 20:49         ` Kanoj Sarcar
2000-06-21 20:59           ` Timur Tabi
2000-06-21 21:10             ` Kanoj Sarcar
2000-06-21 21:28               ` Timur Tabi
2000-06-21 21:41                 ` Kanoj Sarcar
2000-06-21 21:43                   ` Timur Tabi
2000-06-22 19:26                 ` Andrea Arcangeli
2000-06-22 19:51                   ` Jamie Lokier
2000-06-23 17:41                     ` Andrea Arcangeli
2000-06-23 17:52                       ` Jamie Lokier
2000-06-23 18:02                         ` Andrea Arcangeli
2000-06-23 18:03                           ` Andrea Arcangeli
2000-06-22 20:22                   ` Kanoj Sarcar
2000-06-23 18:11                     ` Andrea Arcangeli
2000-06-21 21:22             ` James Manning
2000-06-21 21:24             ` Juan J. Quintela
2000-06-21 21:15 frankeh

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=Pine.LNX.4.10.10006211622270.10983-100000@binx.mbhs.edu \
    --to=akhripin@mbhs.edu \
    --cc=linux-mm@kvack.org \
    --cc=ttabi@interactivesi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox