All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, gerrit@us.ibm.com
Subject: Re: Backport of Ingo/Arjan highpte to 2.4.18 (+O1 scheduler)
Date: Fri, 29 Mar 2002 14:49:07 -0800	[thread overview]
Message-ID: <13110000.1017442147@flay> (raw)
In-Reply-To: <20020326180841.C13052@dualathlon.random>

> I'm not considering to drop pte-highmem from 2.4 and to only support the
> user-fixmaps in 2.5 because it is a showstopper bugfix for lots of
> important users that definitely cannot wait 2.6. I'm also not
> considering backporting the user-fixmaps because that would be a quite
> invasive change messing also with the alignment of the user stack (I
> know it could stay into kernel space, but right after the user stack it
> will be more optimized and cleaner/simpler, so I prefer to put the few
> virtual pages there).

Can you explain the problem with the aligment of the user stack? I can't
see what the problem is here .... and we need to start thinking about how
to fix it if you've seen a problem that we haven't ....

Thanks,

M.



  parent reply	other threads:[~2002-03-29 22:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-21 23:10 Backport of Ingo/Arjan highpte to 2.4.18 (+O1 scheduler) Martin J. Bligh
2002-03-21 23:20 ` Martin J. Bligh
2002-03-26 17:08 ` Andrea Arcangeli
2002-03-26 18:02   ` Martin J. Bligh
2002-03-26 18:18     ` Andrea Arcangeli
2002-03-28 22:48       ` Testing of Ingo/Arjan highpte on 16-way NUMA-Q Martin J. Bligh
2002-03-29 22:49   ` Martin J. Bligh [this message]
2002-03-30 19:44     ` Backport of Ingo/Arjan highpte to 2.4.18 (+O1 scheduler) Andrea Arcangeli
2002-03-31 14:51       ` Andrea Arcangeli

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=13110000.1017442147@flay \
    --to=martin.bligh@us.ibm.com \
    --cc=andrea@suse.de \
    --cc=gerrit@us.ibm.com \
    --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.