All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Variable PTE_FILE_MAX_BITS
Date: Wed, 9 Apr 2003 02:19:38 -0400	[thread overview]
Message-ID: <20030409021938.A19512@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030408225514.478469e0.akpm@digeo.com>; from akpm@digeo.com on Tue, Apr 08, 2003 at 10:55:14PM -0700

> > would you be so kind to take this and forward to Linus?
> > I think this segment of the code is your brainchild.
> 
> y'know, as I was writing that code I thought "no architecture could be dumb
> enough to make PTE_FILE_MAX_BITS variable".

Two different PTE formats.

> > +	/* This needs to be evaluated at runtime on some platforms */
> > +	if (PTE_FILE_MAX_BITS < BITS_PER_LONG)
> > +		if (pgoff + (size >> PAGE_SHIFT) >= (1UL << PTE_FILE_MAX_BITS))
> > +			return err;
> 
> The reason I didn't do this in the first place is that if PTE_FILE_MAX_BITS
> is 32 (as it is for ia32 PAE), the compiler generates a warning about the
> (1<<32).  I guess it generates a bug, too.
> 
> Ho hum.  I shall make it "1ULL".

Wait, that would be a pessimization. Let me think about it. 

I am thinking that perhaps I can arrange is so that the number
bits on different sparcs would end the same.

-- Pete

      reply	other threads:[~2003-04-09  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09  5:16 Variable PTE_FILE_MAX_BITS Pete Zaitcev
2003-04-09  5:55 ` Andrew Morton
2003-04-09  6:19   ` Pete Zaitcev [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=20030409021938.A19512@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=akpm@digeo.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.