All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] CONFIG_IA64_L1_CACHE_SHIFT
Date: Mon, 05 Mar 2001 19:37:39 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005244@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005236@msgid-missing>

>>>>> On Fri, 2 Mar 2001 15:30:18 -0800 , "Grover, Andrew" <andrew.grover@intel.com> said:

  Andrew> In the future, when we have achieved certain functional
  Andrew> power management milestones under Linux and a significant
  Andrew> number of developers have come to understand the complexity
  Andrew> of the ACPI subsystem, it makes sense that the code be
  Andrew> optimized explicitly for the target OS environment. We
  Andrew> expect that this will happen over time for each OS vendor -
  Andrew> the OS vendor should start maintaining and advancing their
  Andrew> OS specific ACPI implementation.

Yes, I agree with this.  My mail wasn't so much meant to critize the
existing code (like you say: it does what it is designed for...) but
to encourage others to think about developing a leaner, more tightly
integrated version for Linux.  I think it would be a nice challenge to
see what could be done in this area, but it would definitely be a
non-trivial project.

	--david


      parent reply	other threads:[~2001-03-05 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-01 19:29 [Linux-ia64] CONFIG_IA64_L1_CACHE_SHIFT Jes Sorensen
2001-03-01 22:35 ` David Mosberger
2001-03-01 23:18 ` Jes Sorensen
2001-03-02  1:00 ` Mallick, Asit K
2001-03-02 15:51 ` David Mosberger
2001-03-02 23:30 ` Grover, Andrew
2001-03-05 19:37 ` David Mosberger [this message]

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=marc-linux-ia64-105590693005244@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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 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.