Date: Tue, 4 Jun 2019 00:15:27 +0200 From: Peter Eriksson <pen@lysator.liu.se> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: RFC: should an incremental reload of exports for mountd be optional? Message-ID: <D685FA4E-0F35-44F8-B341-CF59122E10B9@lysator.liu.se> In-Reply-To: <QB1PR01MB2643E5186098E2AF14934866DD190@QB1PR01MB2643.CANPRD01.PROD.OUTLOOK.COM> References: <QB1PR01MB2643E5186098E2AF14934866DD190@QB1PR01MB2643.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
My vote goes to: Enabled by default (with an option to disable it in case problems pop = up). - Peter > On 31 May 2019, at 23:50, Rick Macklem <rmacklem@uoguelph.ca> wrote: >=20 > Hi, >=20 > I have created a patch for PR#237860 that improves the time it takes = to reload > the exports file(s) for an NFS file server from seconds->milliseconds = by only doing > system calls for the changes to the exports file(s). (Assumes each = reload includes > changes to only a small fraction of the entries.) >=20 > I made it a non-default option of "-I", but asomers@ asked why it = needed to be > optional. >=20 > Basically, I made it optional because I felt the patch might still be = buggy and not > handle some case of an exports file change that I missed. >=20 > However, I can see the argument of making it non-optional (or optional = but enabled > by default) so that sysadmins don't need to add "-I" to avoid long = periods where the > nfsd threads are suspended. > If it is broken, the deamon would need to be restarted to do a full = reload, but that > would also be the case if a sysadmin specified the "-I" option. >=20 > So, the question is... "do you think this should be an option or just = always enabled?". >=20 > Thanks , rick > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D685FA4E-0F35-44F8-B341-CF59122E10B9>