Bump MAXTSIZ.
ClosedPublic
Actions

Authored by trasz on May 16 2017, 5:17 PM.

Details

Reviewers

Commits

rS318398: Bump default MAXTSIZ (kern.maxtsiz) from 128MB to 32GB. The old limit

Summary

Bump default MAXTSIZ (kern.maxtsiz) from 128MB to 32GB. The old limits
prevents one from running eg clang built with debug; the new one is
arbitrary (equal to MAXDSIZ) and... well, should be quite future-proof.

MFC after: 2 weeks

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

trasz created this revision.May 16 2017, 5:17 PM

Herald added a subscriber: imp. · View Herald TranscriptMay 16 2017, 5:17 PM

trasz edited the summary of this revision. (Show Details)May 16 2017, 5:18 PM

trasz added a reviewer: kib.

Harbormaster completed remote builds in B9309: Diff 28423.May 16 2017, 5:59 PM

What about arm64 ?

This revision is now accepted and ready to land.May 16 2017, 8:44 PM

Closed by commit rS318398: Bump default MAXTSIZ (kern.maxtsiz) from 128MB to 32GB. The old limit (authored by trasz). · Explain WhyMay 17 2017, 8:38 AM

This revision was automatically updated to reflect the committed changes.

Hm, for other 64 bit architectures MAXTSIZ seems to be equal to MAXDSIZ already, except that both are 1GB. Not sure if we need to do anything about that then.

On the other hand, the binary was 2.2GB big on amd64, so it _might_ be over the 1GB text size limit. I'll ask about bumping it, I guess.

emaste mentioned this in D28050: Implement enforcing write XOR execute mapping policy..Jan 11 2021, 7:04 PM

Revision Contents
Changeset List

Path

Size

head/

sys/

amd64/

include/

vmparam.h

2 lines

Diff 28453

View Options

head/sys/amd64/include/vmparam.h

Bump MAXTSIZ.ClosedPublicActions