[OpenAFS-Doc] Re: [OpenAFS-devel] vmalloc memory leak in 1.3.84/85?

[Esther Filderman]

Yep, sorry about that. A minor disaster cropped up [I'd forgotten I
had to give a talk last Saturday!!] and I got swamped with that.

I promise I'll get straight on things this weekend.

e.


On 7/28/05, Michael D. Norwick <mnorwick@centurytel.net> wrote:
> Chaskiel M Grundman wrote:
>=20
> >
> >
> > --On Thursday, July 28, 2005 10:00:04 AM -0700 Miles Davis
> > <miles@cs.stanford.edu> wrote:
> >
> >>> you could try enabling pag garbage collection
> >>> sysctl -w afs.GCPAGs=3D1
> >>
> >>
> >> Huh... I had no idea those were there. The default seems to be 2 -- wh=
at
> >> does that mean, and are these documented somewhere?
> >
>=20
> >> Documentation on new features? hah.
> >
> Gee, seems like I had some dialog on this ohhhh, last week?  No
> direction has yet been forthcoming.
>=20
> >>
> >>
> >> 2 is AFS_GCPAGS_USERDISABLED
> >> only a value of 1 (AFS_GCPAGS_OK) will cause the garbage collector to
> >> run. I think that the point of the non-zero disable value is because
> >> the macro AFS_GCPAGS is used both as a compile time directive (#if
> >> AFS_GCPAGS), but is also the initializer for the run-time variable
> >> afs_gcpags (which is what the sysctl modifies and affects the runtime
> >> behavior of the code when it is compile-time enabled). There are
> >> other possible values for afs_gcpags, which indicate that the code
> >> disabled itself due to encountering an error while examining process
> >> lists.
> >
> Michael
> _______________________________________________
> OpenAFS-doc mailing list
> OpenAFS-doc@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-doc
>