All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hammer: MAP_32BIT
Date: Fri, 09 May 2003 15:07:59 -0700	[thread overview]
Message-ID: <3EBC26BF.2080709@zytor.com> (raw)
In-Reply-To: <3EBC2164.6050605@redhat.com>

Ulrich Drepper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> H. Peter Anvin wrote:
> 
> 
>>No, it requires 31-bit addresses, and there was a discussion about how
>>some things need 31-bit and some 32-bit addresses.
> 
> 
> That's completely irrelevant to my point.  Whether MAP_32BIT actually
> has a 31 bit limit or not doesn't matter, it's limited as well in the
> possible mmap blocks it can return.
> 
> The only thing I care about is to have a hint and not a fixed
> requirement for mmap().  All your proposals completely ignored this.
> 

Yes, but this is irrelevant to *MY* point... this discussion spawned a
side discussion, and somehow you're upset that it's not addressing your
concern but a different one... seems a bit ridiculous!

Anyway, I already posted that if we're adding MAP_MAXADDR we could also
add MAP_MAXADDR_ADVISORY or something similar to that.  On the other
hand, how big of a performance issue is it really to call mmap() again
in the failure scenario *only*?

	-hpa



  reply	other threads:[~2003-05-09 21:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09  7:35 hammer: MAP_32BIT Ulrich Drepper
2003-05-09  9:20 ` Andi Kleen
2003-05-09 11:28   ` mikpe
2003-05-09 11:38     ` Andi Kleen
2003-05-09 11:52       ` mikpe
2003-05-09 12:16         ` Andi Kleen
2003-05-09 18:11       ` H. Peter Anvin
2003-05-09 19:24         ` Ulrich Drepper
2003-05-09 20:55           ` H. Peter Anvin
2003-05-09 21:45             ` Ulrich Drepper
2003-05-09 22:07               ` H. Peter Anvin [this message]
2003-05-09 22:20                 ` Ulrich Drepper
2003-05-09 22:21                   ` H. Peter Anvin
2003-05-09 22:20               ` Timothy Miller
2003-05-09 22:20                 ` H. Peter Anvin
2003-05-09 22:46                   ` Timothy Miller
2003-05-09 23:24                     ` H. Peter Anvin
2003-05-13 14:25                       ` Timothy Miller
2003-05-09 22:22                 ` Ulrich Drepper
2003-05-09 22:53                   ` Timothy Miller
2003-05-09 23:24                     ` Ulrich Drepper
2003-05-10  0:00                       ` Edgar Toernig
2003-05-10  0:58                         ` Ulrich Drepper
2003-05-10  2:51                           ` Edgar Toernig
2003-05-09 17:36   ` H. Peter Anvin
2003-05-09 17:39   ` Ulrich Drepper
2003-05-10  1:48     ` Andi Kleen
2003-05-10 20:10       ` David Woodhouse
2003-05-13 18:54         ` H. Peter Anvin

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=3EBC26BF.2080709@zytor.com \
    --to=hpa@zytor.com \
    --cc=drepper@redhat.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.