All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Pryzby <justinpryzby@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: 2.5isms
Date: Fri, 31 Dec 2004 18:06:24 -0500	[thread overview]
Message-ID: <20041231230624.GA29411@andromeda> (raw)

Hi all, I have more 2.5isms for the list.  ./fs/binfmt_elf.c:

  #ifdef CONFIG_X86_HT
                  /*
                   * In some cases (e.g. Hyper-Threading), we want to avoid L1
                   * evictions by the processes running on the same package. One
                   * thing we can do is to shuffle the initial stack for them.
                   *
                   * The conditionals here are unneeded, but kept in to make the
                   * code behaviour the same as pre change unless we have
                   * hyperthreaded processors. This should be cleaned up
                   * before 2.6
                   */

                  if (smp_num_siblings > 1)
                          STACK_ALLOC(p, ((current->pid % 64) << 7));
  #endif

Happy y2k5,
Justin

             reply	other threads:[~2004-12-31 23:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-31 23:06 Justin Pryzby [this message]
2005-01-01  2:34 ` 2.5isms Nick Piggin
2005-01-01  8:40   ` 2.5isms Arjan van de Ven
2005-01-01  9:13   ` 2.5isms Andi Kleen
2005-01-02  0:43     ` 2.5isms Nick Piggin
2005-01-02  8:58       ` 2.5isms Arjan van de Ven
2005-01-03  0:49         ` 2.5isms Nick Piggin
2005-01-02 12:04       ` 2.5isms Andi Kleen
2005-01-03  0:44         ` 2.5isms Nick Piggin
  -- strict thread matches above, loose matches on Subject: below --
2003-07-03 20:01 "Will be removed in 2.4" Justin Pryzby
2003-12-30 21:30 ` 2.5isms Justin Pryzby
2004-01-03 15:18   ` 2.5isms Pavel Machek
2004-01-07  7:28   ` 2.5isms Justin Pryzby
2004-03-29 15:40   ` 2.5isms Pavel Machek

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=20041231230624.GA29411@andromeda \
    --to=justinpryzby@users.sourceforge.net \
    --cc=linux-kernel@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.