Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Wed, Oct 24, 2018 at 08:45:32AM +0200, Igor Gnatenko wrote: > How can I enable cgroups2 on my laptop? Put systemd.unified-cgroup-hierarchy on the kernel command line. Zbyszek > On Fri, Oct 19, 2018, 17:27 Lennart Poettering wrote: > > > On Fr, 19.10.18 09:12, Florian Weimer

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

How can I enable cgroups2 on my laptop? On Fri, Oct 19, 2018, 17:27 Lennart Poettering wrote: > On Fr, 19.10.18 09:12, Florian Weimer (fwei...@redhat.com) wrote: > > > >> (cross-posting to devel and desktop lists, ideally reply to both) > > > > > > Coincidentally, at All Systems Go! in Berlin

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Mo, 22.10.18 11:58, Florian Weimer (fwei...@redhat.com) wrote: > Anyway, the problem suggests to me that the default soft limit should > not be raised until the kernel gets better recovery, so that > applications won't trigger the issue by accident. During the whole discussions we always made

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

* Lennart Poettering: > On Fr, 19.10.18 09:12, Florian Weimer (fwei...@redhat.com) wrote: > >> >> (cross-posting to devel and desktop lists, ideally reply to both) >> > >> > Coincidentally, at All Systems Go! in Berlin last week I had some >> > discussions with kernel people about RLIMIT_NOFILE

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Fr, 19.10.18 09:12, Florian Weimer (fwei...@redhat.com) wrote: > >> (cross-posting to devel and desktop lists, ideally reply to both) > > > > Coincidentally, at All Systems Go! in Berlin last week I had some > > discussions with kernel people about RLIMIT_NOFILE defaults. They > > basically

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

* Lennart Poettering: > On Fr, 05.10.18 19:31, Kamil Paral (kpa...@redhat.com) wrote: > >> (cross-posting to devel and desktop lists, ideally reply to both) > > Coincidentally, at All Systems Go! in Berlin last week I had some > discussions with kernel people about RLIMIT_NOFILE defaults. They >

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

* Kamil Paral: > From a technical point of view I'm not able to judge whether raising > the fileno limits by default is a trivial change or something with > important security implications. It has implications for reliability (and perhaps security). File descriptors can refer to sockets, and

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Thu, Oct 18, 2018 at 11:51:57AM +0200, Lennart Poettering wrote: > On Do, 18.10.18 11:34, Kamil Paral (kpa...@redhat.com) wrote: > > > > We merged the PR that bumps RLIMIT_NOFILE to 256K into systemd > > > upstream yesterday. It should trickle into Fedora and the other > > > distros as soon as

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Do, 18.10.18 11:34, Kamil Paral (kpa...@redhat.com) wrote: > > We merged the PR that bumps RLIMIT_NOFILE to 256K into systemd > > upstream yesterday. It should trickle into Fedora and the other > > distros as soon as we do the next release. > > > > https://github.com/systemd/systemd/pull/10244

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Thu, Oct 18, 2018 at 9:48 AM Lennart Poettering wrote: > On Mi, 17.10.18 20:35, Zebediah Figura (z.figur...@gmail.com) wrote: > > > I do not, no. That number came up pretty early in testing, and I think we > > ended up leaving the limit at ~1M while testing other applications. On > the > >

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Mi, 17.10.18 20:35, Zebediah Figura (z.figur...@gmail.com) wrote: > I do not, no. That number came up pretty early in testing, and I think we > ended up leaving the limit at ~1M while testing other applications. On the > other hand, I know many users in the wild have used ~200k values, and I >

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On 10/16/18 6:25 AM, Kamil Paral wrote: On Mon, Oct 15, 2018 at 7:34 PM Lennart Poettering > wrote: On Mo, 15.10.18 18:00, Kamil Paral (kpa...@redhat.com ) wrote: > On Tue, Oct 9, 2018 at 6:15 PM Lennart Poettering

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Mon, Oct 15, 2018 at 7:34 PM Lennart Poettering wrote: > On Mo, 15.10.18 18:00, Kamil Paral (kpa...@redhat.com) wrote: > > > On Tue, Oct 9, 2018 at 6:15 PM Lennart Poettering > > wrote: > > > > > On Di, 09.10.18 14:45, Anderson, Charles R (c...@wpi.edu) wrote: > > > > > > > > It would be

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Mo, 15.10.18 18:00, Kamil Paral (kpa...@redhat.com) wrote: > On Tue, Oct 9, 2018 at 6:15 PM Lennart Poettering > wrote: > > > On Di, 09.10.18 14:45, Anderson, Charles R (c...@wpi.edu) wrote: > > > > > > It would be nice if somebody managed to find where this is patched in > > > > Debian.

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Mon, Oct 15, 2018 at 06:00:05PM +0200, Kamil Paral wrote: > On Tue, Oct 9, 2018 at 6:15 PM Lennart Poettering > wrote: > > > On Di, 09.10.18 14:45, Anderson, Charles R (c...@wpi.edu) wrote: > > > > > > It would be nice if somebody managed to find where this is patched in > > > > Debian.

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Tue, Oct 9, 2018 at 6:15 PM Lennart Poettering wrote: > On Di, 09.10.18 14:45, Anderson, Charles R (c...@wpi.edu) wrote: > > > > It would be nice if somebody managed to find where this is patched in > > > Debian. Because I somewhat doubt that they made this change without a > > > proper

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Di, 09.10.18 14:45, Anderson, Charles R (c...@wpi.edu) wrote: > > It would be nice if somebody managed to find where this is patched in > > Debian. Because I somewhat doubt that they made this change without a > > proper discussion. And Debian is very much server oriented. > > Can we not have

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On 10/9/18 0810 UTC, Daniel P. Berrangé wrote: AFAICT, the TCP receive buffer size is about 200 KB per socket. With the current nfile=4096, it looks like a single process can already consume 200 KB * 4096 = ~800 MB of RAM just by using TCP sockets. IOW, does the nfiles limit make a real world

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Tue, Oct 09, 2018 at 04:08:06PM +0200, Kamil Paral wrote: > On Tue, Oct 9, 2018 at 3:29 PM Michal Konečný wrote: > > > Because this is mainly for Steam Proton I support the decision to raise > > the limit only for Workstation. No need to do this on server edition. > > I recommend to also

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Tue, Oct 9, 2018 at 3:29 PM Michal Konečný wrote: > Because this is mainly for Steam Proton I support the decision to raise > the limit only for Workstation. No need to do this on server edition. > I recommend to also raise this limit for Silverblue edition, because this > is targeted on

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On 9.10.2018 15:14, Jan Pokorný wrote: On 08/10/18 18:28 -0500, Zebediah Figura wrote: On 08/10/18 16:43, John Reiser wrote: On 10/8/18 2026 UTC, Zebediah Figura wrote: On 08/10/18 2000 UTC, John Reiser wrote: Allowing 1M open files per unprivileged process is too many. Megabytes of RAM

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On 08/10/18 18:28 -0500, Zebediah Figura wrote: > On 08/10/18 16:43, John Reiser wrote: >> On 10/8/18 2026 UTC, Zebediah Figura wrote: >>> On 08/10/18 2000 UTC, John Reiser wrote: Allowing 1M open files per unprivileged process is too many. Megabytes of RAM are precious.  A hard

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Mon, Oct 08, 2018 at 01:00:01PM -0700, John Reiser wrote: > Allowing 1M open files per unprivileged process is too many. > > Megabytes of RAM are precious. A hard limit of 1M open files per process > allows each process to eat at least 256MB (1M * sizeof(struct file) > [linux/fs.h]) of RAM.

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On 08/10/18 16:43, John Reiser wrote: > On 10/8/18 2026 UTC, Zebediah Figura wrote: >> On 08/10/18 2000 UTC, John Reiser wrote: >>> Allowing 1M open files per unprivileged process is too many. >>> >>> Megabytes of RAM are precious.  A hard limit of 1M open files per >>> process >>> allows each

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On 10/8/18 2026 UTC, Zebediah Figura wrote: On 08/10/18 2000 UTC, John Reiser wrote: Allowing 1M open files per unprivileged process is too many. Megabytes of RAM are precious.  A hard limit of 1M open files per process allows each process to eat at least 256MB (1M * sizeof(struct file)

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On 08/10/18 15:00, John Reiser wrote: > Allowing 1M open files per unprivileged process is too many. > > Megabytes of RAM are precious.  A hard limit of 1M open files per process > allows each process to eat at least 256MB (1M * sizeof(struct file) > [linux/fs.h]) of RAM.  If a single user is

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

Allowing 1M open files per unprivileged process is too many. Megabytes of RAM are precious. A hard limit of 1M open files per process allows each process to eat at least 256MB (1M * sizeof(struct file) [linux/fs.h]) of RAM. If a single user is allowed 1000 processes, then that's 256GB of RAM,

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

Hi all, My thanks as well to Kamil for raising the question; it's been on my list of things to do for a while. The design of my patch set necessitates the allocation of one eventfd descriptor for each kernel handle (which is, sort of, the Windows equivalent of an fd) associated with a sync

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Mon, Oct 8, 2018 at 11:09 AM Michal Konečný wrote: > Maybe it will be also good to look at the SteamOS distribution and what > limits they are using. > According to the proton document [1], SteamOS also has an increased fileno hard limit. I haven't verified the actual value, but they

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

Maybe it will be also good to look at the SteamOS distribution and what limits they are using. On 8.10.2018 10:53, Kamil Paral wrote: On Fri, Oct 5, 2018 at 10:20 PM Lennart Poettering mailto:mzerq...@0pointer.de>> wrote: I have thus prepared this a few days ago:

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Fri, Oct 5, 2018 at 10:20 PM Lennart Poettering wrote: > I have thus prepared this a few days ago: > > https://github.com/systemd/systemd/pull/10244 This is great, thank you. So, any idea why they picked 1M? Are there typical apps that require > really that many? > I've emailed Zebediah

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On 10/05/2018 11:03 AM, Lennart Poettering wrote: On Fr, 05.10.18 19:31, Kamil Paral (kpa...@redhat.com) wrote: (cross-posting to devel and desktop lists, ideally reply to both) Coincidentally, at All Systems Go! in Berlin last week I had some discussions with kernel people about

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Fr, 05.10.18 12:28, Nicholas Miell (nmi...@gmail.com) wrote: > >> This is not quite the 1M you appear to ask for though… I picked 256K > >> mostly because I wanted to stay lower than the kernel built-in max > >> (which is 1M, i.e. /proc/sys/fs/nr_open), and needed to pick > >> something. Do

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On 10/5/18 11:55 AM, Michael Cronenworth wrote: > First off, thanks, Kamil, for starting this discussion. I've been > meaning to bring it up. > > On 10/5/18 1:03 PM, Lennart Poettering wrote: > [snip] >> This is not quite the 1M you appear to ask for though… I picked 256K >> mostly because I

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

First off, thanks, Kamil, for starting this discussion. I've been meaning to bring it up. On 10/5/18 1:03 PM, Lennart Poettering wrote: [snip] This is not quite the 1M you appear to ask for though… I picked 256K mostly because I wanted to stay lower than the kernel built-in max (which is 1M,

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Fr, 05.10.18 19:31, Kamil Paral (kpa...@redhat.com) wrote: > (cross-posting to devel and desktop lists, ideally reply to both) Coincidentally, at All Systems Go! in Berlin last week I had some discussions with kernel people about RLIMIT_NOFILE defaults. They basically suggested that the

Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

On Fri, Oct 5, 2018 at 11:31 AM, Kamil Paral wrote: > (cross-posting to devel and desktop lists, ideally reply to both) > Debian and Ubuntu: > I've installed both Debian (Sid) and Ubuntu (18.10) to verify this, and can > confirm it. The default soft limit stays the same (1024), but the hard

raise fileno limit to make Steam Proton / Wine+esync work well in Fedora

(cross-posting to devel and desktop lists, ideally reply to both) Hello, this is a request for feedback regarding adjusting process limits to make Steam/Wine work better on Fedora. *A quick background:* In August Valve announced [1] Proton [2], their own fork of Wine, to get included in their