Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Jul 2003 10:47:23 -0500 (CDT)
From:      Mike Silbersack <silby@silby.com>
To:        "Daniel C. Sobral" <dcs@tcoip.com.br>
Cc:        arch@freebsd.org
Subject:   Re: 4.x mbuf binary compatibility; can it be broken?
Message-ID:  <20030715104206.C14114@odysseus.silby.com>
In-Reply-To: <3F13E69D.3050001@tcoip.com.br>
References:  <20030714164426.R8225@odysseus.silby.com> <3F13E69D.3050001@tcoip.com.br>

next in thread | previous in thread | raw e-mail | index | archive | help

On Tue, 15 Jul 2003, Daniel C. Sobral wrote:

> I think that breaking the ABI at the winter of 4.x is a bad idea. It
> would be bad at it's spring, but given the seriousness of the matter,
> perhaps a necessity. At this point, though? Dubious proposition...
>
> --
> Daniel C. Sobral                   (8-DCS)

Well, as it turns out, the machine which is actively exhibiting the
problem has had a NIC swap is went into active service, so I won't be
getting the test results which might justify an ABI breakage too soon.

In the meantime, I've been looking more, and it appears that I should be
able to hack around the limit without breaking the ABI.  (There may be a
performance penalty, but it should be extremely minor.)

Mike "Silby" Silbersack



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030715104206.C14114>