public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Joe Korty <joe.korty@ccur.com>
Cc: linux-kernel@vger.kernel.org, the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH] x86: Change thread_info's flag field back to 32 bits
Date: Thu, 4 Dec 2008 11:06:20 +0100	[thread overview]
Message-ID: <20081204100620.GA17634@elte.hu> (raw)
In-Reply-To: <20081203235819.GA17615@tsunami.ccur.com>


* Joe Korty <joe.korty@ccur.com> wrote:

> Change x86_64's thread_info 'flags' field back to __u32.
> 
> This was changed to 'unsigned long' when the thread_info*.h
> for i386 and x86_64 were merged.  Change it back.  We can
> do this as only 27 bits of 'flags' are actually used.
> 
> This change actually packs down thread_info by 64 bits:
> 32 bits are saved by the smaller flags, and 32 bits are
> saved by the following 'mm_segment_t field' becoming
> naturally 64-bit aligned.
> 
> Signed-off-by: Joe Korty <joe.korty@ccur.com>

applied, thanks Joe!

	Ingo

      reply	other threads:[~2008-12-04 10:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 23:58 [PATCH] x86: Change thread_info's flag field back to 32 bits Joe Korty
2008-12-04 10:06 ` Ingo Molnar [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=20081204100620.GA17634@elte.hu \
    --to=mingo@elte.hu \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox