[OpenAFS] Current Limits of OpenAfs ?
gary mazzaferro
garym@oedata.com
Sat, 10 Jan 2009 19:10:51 -0800
------=_Part_52136_8367268.1231643451283
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Thanks Derrick,
So basically, its one callback state per file and one per RO volume. I'm
assuming that the server with the RO volume will not be maintaining the
state of the server with open files and likewise the server with open files
will not be mainataining the state of the RO volumes.
So, the question is... what is the resource consumption for each callback
state ?
cheers
On Sat, Jan 10, 2009 at 7:58 AM, Derrick Brashear <shadow@gmail.com> wrote:
> > Can anyone tell me how to calculate the memory requirement for each
> client
> > on a server ?
>
> Not without more information. The state information is stored per
> callback, which is one per file/directory in a writable volume, and
> one per entire readonly volume, so without knowing what the client's
> utilization will be, I can't say.
> >
> > Are the file ACLs the underlying native ux ACLs or are AFS's file ACLs
> > layered on top ?
>
> AFS acls are by directory. Unix mode bits are there but not enforced by
> AFS.
> >
> > The question is really for eval'ing AFS over ZFS and direct support for
> > WIndows/Samba ACLs.
> >
> > Is there a time table for the file ACL support ?
>
> Some work was done last summer but to the moment there has been no
> further progress, and the work from last summer at this point is
> effectively only design work.
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>
------=_Part_52136_8367268.1231643451283
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Thanks Derrick,<br><br>So basically, its one callback state per file and one per RO volume. I'm assuming that the server with the RO volume will not be maintaining the state of the server with open files and likewise the server with open files will not be mainataining the state of the RO volumes. <br>
<br>So, the question is... what is the resource consumption for each callback state ? <br><br>cheers<br><br><br><br><div class="gmail_quote">On Sat, Jan 10, 2009 at 7:58 AM, Derrick Brashear <span dir="ltr"><<a href="mailto:shadow@gmail.com">shadow@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">> Can anyone tell me how to calculate the memory requirement for each client<br>
> on a server ?<br>
<br>
</div>Not without more information. The state information is stored per<br>
callback, which is one per file/directory in a writable volume, and<br>
one per entire readonly volume, so without knowing what the client's<br>
utilization will be, I can't say.<br>
<div class="Ih2E3d">><br>
> Are the file ACLs the underlying native ux ACLs or are AFS's file ACLs<br>
> layered on top ?<br>
<br>
</div>AFS acls are by directory. Unix mode bits are there but not enforced by AFS.<br>
<div class="Ih2E3d">><br>
> The question is really for eval'ing AFS over ZFS and direct support for<br>
> WIndows/Samba ACLs.<br>
><br>
> Is there a time table for the file ACL support ?<br>
<br>
</div>Some work was done last summer but to the moment there has been no<br>
further progress, and the work from last summer at this point is<br>
effectively only design work.<br>
<div><div></div><div class="Wj3C7c">_______________________________________________<br>
OpenAFS-info mailing list<br>
<a href="mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</a><br>
<a href="https://lists.openafs.org/mailman/listinfo/openafs-info" target="_blank">https://lists.openafs.org/mailman/listinfo/openafs-info</a><br>
</div></div></blockquote></div><br>
------=_Part_52136_8367268.1231643451283--