All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mallick, Asit K" <asit.k.mallick@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] CONFIG_IA64_L1_CACHE_SHIFT
Date: Fri, 02 Mar 2001 01:00:44 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005240@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005236@msgid-missing>

Also this is configurable to take care of future processors that may have
higher cache line sizes.

Thanks,
Asit


> -----Original Message-----
> From: David Mosberger [mailto:davidm@hpl.hp.com]
> Sent: Thursday, March 01, 2001 2:35 PM
> To: Jes Sorensen
> Cc: linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] CONFIG_IA64_L1_CACHE_SHIFT
> 
> 
> >>>>> On 01 Mar 2001 20:29:28 +0100, Jes Sorensen 
> <jes@linuxcare.com> said:
> 
>   Jes> Hi Anyone who can explain why there is a
> 
>   Jes> define_int CONFIG_IA64_L1_CACHE_SHIFT 6
> 
>   Jes> in the config file? We already have SMP_CACHE_BYTES and
>   Jes> L1_CACHE bytes for all architectures, it doesn't make a whole
>   Jes> lot of sense to me ot invent yet another alignment rule.
> 
> $ fgrep CONFIG_IA64_L1 include/asm-ia64/cache.h 
> #define L1_CACHE_SHIFT          CONFIG_IA64_L1_CACHE_SHIFT
> 
> 	--david
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 


  parent reply	other threads:[~2001-03-02  1:00 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 [this message]
2001-03-02 15:51 ` David Mosberger
2001-03-02 23:30 ` Grover, Andrew
2001-03-05 19:37 ` David Mosberger

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-105590693005240@msgid-missing \
    --to=asit.k.mallick@intel.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.