introducing chuck silvers

[Chuck Silvers]

On Tue, May 29, 2012 at 02:38:24PM -0600, Justin T. Gibbs wrote:
> PRs often (unfortunately) get lost.  If you can provide an enumeration of your
> changes, I can introduce you to a committer that works in that area to help get
> the changes into the tree.

thanks, that will be great.  here's our list of patches:

 - fixes and enhancements to the aesni driver
   - replace the asm version of aesni_decrypt_cbc() with a C wrapper
     around aesni_dec() (like aesni_encrypt_cbc() was already a wrapper
     around aesni_enc()) since using the asm one often crashed mysteriously
     for us.
   - allow using the same aesni session from multiple CPUs simultaneously
     by moving the saved FPU context from the session to the stack.
   - mark aesni as CRYPTOCAP_F_SYNC since it is synchronous.

 - enhance the NFS server to support multiple writes to the same file
   in parallel if the underlying fs supports it.  this builds on top of
   the addition of a "flags" parameter to VFS_FHTOVP() that I backported
   from -current to our 8.2-based tree.

 - allow adjusting NKPT via the kernel config file on amd64 too.

 - have uuidgen ignore ipfw0 when looking for a MAC address.
   (this only shows up when ipfw is built into the kernel and all the
    interfaces with real MAC addresses are from modules.)


there are a couple minor ZFS ones, I'll send those here separately.

some of these are really more workarounds than fixes,
but you get the idea.

we also have a fix for the open-vm-tools vmxnet driver to support
more than 4GB of RAM.  I suppose I should push that back to the
sourceforge project as well as the freebsd ports tree.

we also built several other ports (php5-* and py26-django) without gettext
or libiconv (to avoid GPL3).  I don't know if these are interesting to
anyone else.

I also ported the openbsd "vmt" driver to freebsd since that was easier
than getting the open-vm-tools vmtoolsd to build without libiconv.

I think that's all so far.


> Longer term, we should figure out how to make you a committer. :-)

I'm happy to feed our changes back through other folks. :-)

-Chuck