[OpenAFS-devel] Re: IPv6 support

[Andrew Deason]

On Mon, 14 Feb 2011 16:33:14 +0000
Simon Wilkinson <sxw@inf.ed.ac.uk> wrote:

> I think the problem is that such an audit of the entire code base is  
> likely to be a considerable amount of work, and require a reasonable  
> depth of understanding of the code. For example, it's far from clear  
> to the untrained eye which structures are serialised to disk, or are  
> part of a Ubik database, and which are purely held in memory for the  
> life of a process.

Not to mention that I don't think I could come up with a more dull
project if I tried (IMO :). But I won't deny it'd be nice if all ipv4
addresses were in a type that clearly says that, instead of just being
'afs_int32' everywhere.

> > 64-bit native server binaries?
> > I assume most of this is going through the code and checking types  
> > and code clean up, fixing alignment errors, etc.
> 
> I was pretty sure we did 64bit native binaries already. We've
> certainly been fixing bug reports related to 64bit support as we
> receive them (most recently in supergroups), but these seem to be in
> relatively untrodden areas of the code. Do we really still have 64bit
> issues on some platforms?

We only build 32-bit binaries on Solaris, but it's being worked on. I
think there's a discussion to be had about how the user specifies this,
though... it's not optimal to just use 64-bit binaries everywhere you
can.

I'm not aware of any other platforms, though. At least, none I've heard
anyone ask about.

> There are a number of hurdles to jump before even applying to Google.  
> We need mentors. Please don't assume that those people who mentored in  
> previous years will do so this year - many of us are significantly  
> busier this year than last, and mentoring is a significant time  
> commitment. Without a reasonable pool of mentors, there's no way that  
> we can make a credible application to Google.

What is the timeline we're dealing with here? What are the deadlines we
need to know stuff by?

-- 
Andrew Deason
adeason@sinenomine.net