all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>
Cc: Rahguzar <rahguzar@zohomail.eu>, 72278@debbugs.gnu.org
Subject: bug#72278: 29.4; Proced reports incorrect results with 16KB page size
Date: Fri, 26 Jul 2024 18:33:09 -0400	[thread overview]
Message-ID: <CADwFkmnFMe0Ez0ZJg1zNYcL40fMzBues4QLUYCP3-cBiYCZQ9A@mail.gmail.com> (raw)
In-Reply-To: <eac72c56-b412-4ec9-b14a-b53ae3844b88@cs.ucla.edu>

Paul Eggert <eggert@cs.ucla.edu> writes:

> On 2024-07-25 02:55, Stefan Kangas wrote:
>> On Linux, page sizes can vary per process ("multiple page size
>> support").  Should we bother with that?
>
> I thought that support didn't change what getpagesize returns or what
> /proc/PID/stat reports, at least not in mainline Linux kernels. Am I
> missing something?

I don't know to be honest, which is why I'm asking.  If you think using
getpagesize is all that we need then that's good enough for me.





  reply	other threads:[~2024-07-26 22:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24 17:22 bug#72278: 29.4; Proced reports incorrect results with 16KB page size Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-24 19:29 ` Stefan Kangas
2024-07-24 20:40   ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25  9:12     ` Stefan Kangas
2024-07-25  9:39       ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25  5:06 ` Eli Zaretskii
2024-07-25  6:38   ` Paul Eggert
2024-07-25  9:55     ` Stefan Kangas
2024-07-25 14:47       ` Paul Eggert
2024-07-26 22:33         ` Stefan Kangas [this message]
2024-07-27  1:40           ` Paul Eggert

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=CADwFkmnFMe0Ez0ZJg1zNYcL40fMzBues4QLUYCP3-cBiYCZQ9A@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=72278@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=rahguzar@zohomail.eu \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.