| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Reducing the chunk header sizes on all memory context types |
| Date: | 2022-10-07 00:50:11 |
| Message-ID: | CAApHDvqhOF+6-eo7O7s2gEkYkj1vBhfrByU=cAuszoe62tM87Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 7 Oct 2022 at 12:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Which leaves me with the attached proposed wording.
No objections here.
With these comments I'd be using slot MCTX_UNUSED4_ID first, then I'd
probably be looking at MCTX_UNUSED5_ID after adjusting wipe_mem to do
something other than setting bytes to 0x7F. I'd then use
MCTX_UNUSED3_ID since that pattern is only used for larger chunks with
glibc (per your findings). After that, I'd probably start looking
into making more than 3 bits available. If that wasn't possible, I'd
be using MCTX_UNUSED2_ID and at last resort MCTX_UNUSED1_ID.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-10-07 01:00:14 | Re: Reducing the chunk header sizes on all memory context types |
| Previous Message | Ranier Vilela | 2022-10-07 00:35:25 | Re: Avoid mix char with bool type in comparisons |