Bug 774

Summary:

RFE: Xserver should have an option to define the page size and default to 64KB

Product:

xorg

Reporter:

Roland Mainz <roland.mainz>

Component:

Server/General

Assignee:

Xorg Project Team <xorg-team>

Status:

RESOLVED WONTFIX

QA Contact:

Xorg Project Team <xorg-team>

Severity:

enhancement

Priority:

high

CC:

alan.coopersmith

Version:

git

Keywords:

cleanup0407

Hardware:

SPARC

OS:

Solaris

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
multipagesize.c - quick&dirty hack which shows how to set the page size for stack&&heap (use % pmap -s <pid> # to verify...)	none
Prototype patch for 2004-10-09-trunk	none

Description Roland Mainz 2004-06-20 19:02:27 UTC

RFE: The Xserver should have an option to define the page size (on systems which
support multiple page size) and default to 64KB (e.g. anything better than the
"default" 8KB page size).

Comment 1 Roland Mainz 2004-06-20 21:28:13 UTC

Created attachment 394 [details]
multipagesize.c - quick&dirty hack which shows how to set the page size for stack&&heap (use % pmap -s <pid> # to verify...)

Comment 2 Roland Mainz 2004-10-09 00:03:48 UTC

Created attachment 1045 [details] [review]
Prototype patch for 2004-10-09-trunk

The patch adds a new "-pagesize" option on platforms with MPSS API support
(=Solaris) and sets the default to 512k pages.

Comment 3 Daniel Stone 2007-02-27 01:23:40 UTC

Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.

Comment 4 Daniel Stone 2007-04-07 14:23:42 UTC

alan, since it's only available on solaris, your call: is there any point in applying it?

Comment 5 Alan Coopersmith 2007-04-09 13:48:25 UTC

I don't think we need this on Solaris, since we have the generic ppgsz tool to set
preferred page sizes for processes without having to modify every process to set
it's preferred page sizes.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.