17:01:29 #startmeeting FESCO (2023-05-16) 17:01:29 Meeting started Tue May 16 17:01:29 2023 UTC. 17:01:29 This meeting is logged and archived in a public location. 17:01:29 The chair is zbyszek. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:01:29 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:01:29 The meeting name has been set to 'fesco_(2023-05-16)' 17:01:29 #meetingname fesco 17:01:29 The meeting name has been set to 'fesco' 17:01:29 #chair nirik, decathorpe, zbyszek, sgallagh, mhroncok, dcantrell, music, mhayden, Conan_Kudo, Pharaoh_Atem, Son_Goku, King_InuYasha, Sir_Gallantmon, Eighth_Doctor 17:01:29 Current chairs: Conan_Kudo Eighth_Doctor King_InuYasha Pharaoh_Atem Sir_Gallantmon Son_Goku dcantrell decathorpe mhayden mhroncok music nirik sgallagh zbyszek 17:01:32 #topic init process 17:01:46 .hello2 17:01:47 mhayden: mhayden 'Major Hayden' 17:01:48 .hello churchyard 17:01:51 mhroncok: churchyard 'Miro Hrončok' 17:01:59 morning 17:02:00 .hello2 17:02:00 zbyszek: zbyszek 'Zbigniew Jędrzejewski-Szmek' 17:02:34 We're at 4/9 17:03:34 Eighth_Doctor: meeting 17:03:51 decathorpe, sgallagh, dcantrell, music: meeting 17:03:59 I will not be able to stick around much 17:04:09 gotta head out to exam testing 17:04:36 .hello2 17:04:39 aleasto: aleasto 'Alessandro Astone' 17:04:47 .hello ngompa 17:04:48 Eighth_Doctor: ngompa 'Neal Gompa' 17:05:14 OK, should we start? With Neal, we theoretically have quorum… 17:05:23 But we might not be able to pass anything. 17:05:43 aleasto: thanks for coming 17:05:49 aleasto++ 17:05:49 zbyszek: Karma for aleasto changed to 1 (for the release cycle f38): https://badges.fedoraproject.org/tags/cookie/any 17:06:03 :) 17:06:18 .hello music 17:06:19 music[m]: music 'Benjamin Beasley' 17:06:27 aleasto++ 17:06:27 mhayden: Karma for aleasto changed to 2 (for the release cycle f38): https://badges.fedoraproject.org/tags/cookie/any 17:06:32 OK, so now we have 6.5/9, let's go! 17:06:38 #topic #2994 Change: BiggerESP 17:06:38 .fesco 2994 17:06:39 zbyszek: Issue #2994: Change: BiggerESP - fesco - Pagure.io - https://pagure.io/fesco/issue/2994 17:07:09 hey, I'm also here, will be at my PC in a few minutes. 17:07:14 * nirik was +1 in ticket, still am. 17:07:35 There were 5 +1 votes in the ticket. 17:08:03 I'm OK with being overvoted on this. I don't think that this is a terrible change, but also it's just another stop-gap half-solution. 17:08:32 I'm worried something will break with making the ESP bigger 17:08:36 0. I just got back from PTO and I wasn't abel to keep up with anything fesco much 17:08:36 yeah, it is... but we need it until we can do some better longer term one IMHO 17:08:40 I'd rather see us figure that out and be able to revert it easily if needed 17:10:19 I'd like us to just make one bigger partition. But if that causes problems, obviously taht'd be bad. So in this regard, growing the ESP first is a good test. 17:10:50 I already know that we have problems with really large ESPs in the cloud EFI firmware 17:11:04 and I suspect we're going to have some problems on that front in physical servers 17:11:15 and laptops too 17:11:20 but we'll find out as we try this 17:12:54 Eighth_Doctor: you mentioned arm. Was it arm64 or arm32? 17:13:00 arm64 17:14:09 Well, OK. I don't have the energy to fight for something better. 17:14:56 Should we vote? 17:15:47 I see zbyszek’s point as valid, and several people’s points in favor as valid. A few of you understand this change better than I do. It still seems basically OK overall to me. 17:16:33 .hi 17:16:33 Eighth_Doctor: was it with FAT32 or FAT16? Because FAT16 should be good for 4GB, so maybe we don't need FAT32. 17:16:34 sgallagh: sgallagh 'Stephen Gallagher' 17:16:58 I'm weakly +1 to this. I think there are risks, but there are also risks to doing nothing. 17:17:16 perhaps we could do 500 on x86 and less/whatever it is now on arm? but that would be kinda confusing... 17:17:17 Yeah, doing nothing is the worst option. 17:19:21 OK. Let's vote. 17:19:28 PROPOSAL: APPROVE 17:19:37 0 17:19:53 +1 (as in the ticket) 17:20:06 +1 17:20:11 +1 17:20:11 +1 17:20:24 Eighth_Doctor? 17:21:49 (I'd like to vote 0, but that'd be nasty, because there was +5 in the ticket, so we'd fall short purely because of procedural reasons.) 17:22:09 +1 17:22:17 I think we can count +1s from the ticket as well 17:22:25 I don't think we do this normally. 17:22:28 0 17:22:30 ok 17:22:41 #agree APPROVED (+5, 2, 0) 17:23:05 I think we would want to change this, i.e. keep votes from the ticket unless revoked, but that's a separate discussion. 17:23:15 #topic #2993 Change: Increase vm.max_map_count value 17:23:15 .fesco 2993 17:23:16 zbyszek: Issue #2993: Change: Increase vm.max_map_count value - fesco - Pagure.io - https://pagure.io/fesco/issue/2993 17:23:44 I think we need more info and there wasn't much in the devel thread in the way of answers, so -1 from me for now... 17:23:53 We have aleasto here 17:24:22 zbyszek: Thank you for keeping eyes on the big picture. Your dissent is valuable. 17:24:31 i've tracked down the source of the current value: https://github.com/torvalds/linux/blob/v2.6.12-rc2/include/linux/sched.h#L190 17:24:40 "This is a random (large) number" 17:25:07 * mhayden enjoys the descriptive comment provided 17:25:31 https://xkcd.com/221/ 17:25:32 That is true. But that's a very big step to 2147483642. 17:25:39 I'd be interested in the reason for bumping the limit to 4 billion instead of some more "limited" raise to a few million 17:25:49 yeah. 17:26:06 And also, with the raised limit, what happens with the reproducer posted by Florian Weimer. Does the machine go down? 17:26:15 the issues for games I saw referenced values as high as ~16 million, which is far from 4 billion 17:26:36 i haven't tried the reproducer 17:26:58 zbyszek: I would also like to know the answer to that for any proposed lower value. 17:27:07 -1 to the proposal as is 17:27:20 I have to leave now for a couple minutes, sorry, this was unexpected 17:27:48 OK, so aleasto, can you do some more research and come back with an amended proposal and results of checks? 17:28:12 i think the research would have to sending an RFC to lkml 17:28:20 s/have to/have to be/ 17:28:25 which sure, i can do 17:28:50 No, research as in setting some values and trying to crash a system in one or two configurations. 17:29:41 ok 17:29:53 We have done various changes to the system respond properly to memory overload. We have early-oom/oomd, and some resource separation, etc. 17:30:19 We don't want to open an easy avenue of making the system crash or become nonresponsive. 17:30:25 i saw we also just changed the oomd kill threshold 17:31:00 That's a different story: oomd is too agressive when we have zram, but no real swap. So we're effectively making it less likely to act. 17:31:12 in the tests I think it was noted that oomd killer doesn't handle this case right? 17:31:17 Yeah. 17:31:38 yea which sounds like a bug in oomd 17:31:46 i mean why should the map count matter 17:31:52 but yea i can try different values... 17:32:20 what i won't be able to try is running the affected steam games i don't own :p 17:32:49 I think we can assume that if we raise it enough, they will run. 17:32:51 Sadly, FESCo doesn't have the budget to buy you games for testing :) 17:33:02 The question is how this affects non-game use. 17:33:23 #action aleasto to try with different settings, check machine stability. 17:33:27 OK? 17:33:55 i think the value is purely an implementation detail of vma 17:34:02 also based on the in-line comment 17:34:26 It is also possible that the machine crashes with the current default too. 17:34:37 Then we have a bigger problem. 17:34:45 But somebody needs to check that. 17:35:03 ok 17:35:30 Unless there's more comments, I'll move to the next topic. 17:35:52 thanks aleasto! 17:36:00 Yep, thanks aleasto. 17:36:01 #topic Next week's chair 17:36:12 Volunteers? 17:36:19 A volunteer? 17:36:45 I'll do it 17:36:49 Thanks! 17:36:57 #action sgallagh will chair the next meeting 17:37:01 #topic Open Floor 17:37:48 If nothing, let's wrap this up. 17:38:06 Thanks everyone. 17:38:11 #endmeeting