public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Sarnath  Kannan" <sparc64@rediffmail.com>
To: gcc@gcc.gnu.org
Subject: Compiler directed Page coloring
Date: Fri, 28 Mar 2003 10:53:00 -0000	[thread overview]
Message-ID: <20030328070915.17078.qmail@mailweb33.rediffmail.com> (raw)

Hi,
  I am new to this group.
  For quite a while, I have been thinking about "compiler
  directed page coloring" which could be used to enhance
  performance of GNU/Linux system. One can implement 
page-coloring
  in the Linux kernel with the help of 
application-specific-inputs
  from GCC. Such models had already been researched and 
investigate by
  many scholars. (Please check out "citeseer" and Google for more 
info)

  I have a few questions:
  1) Is this mailing list the correct place for this suggestion 
?
  2) Are any of you interested in this idea ?
  3) If so, What sort of inputs can GCC to the kernel w.r.t page
     coloring ? Can It be done ? I think "Flow graphs",
     "tracking data access, and other subtle nuances come into 
picture.
     Can such information be given by GCC ? I dont know anything 
about
     GCC internals. I am a mere user.
  4) In case one starts to implement, we need to take help from 
the
     linux-kernel guys so that we evolve a proper model for this 
and
     develop the entire thing independently. People from both 
areas
     may need to work in testing/benchmarking etc.. So Is this 
all
     possible (given the limited resources of developers and 
their
     work load)

Thanks for any feedback,
Pardon me if this is out of context of the group.
/ /
Sarnath


---------------------------
You CAN if u think u CAN !
----------------------------
_______________________________________________________________________
Odomos - the only  mosquito protection outside 4 walls -
Click here to know more!
http://r.rediff.com/r?http://clients.rediff.com/odomos/Odomos.htm&&odomos&&wn

                 reply	other threads:[~2003-03-28  7:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030328070915.17078.qmail@mailweb33.rediffmail.com \
    --to=sparc64@rediffmail.com \
    --cc=gcc@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).