Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Dec 2013 12:16:57 -0600
From:      Mark Felder <feld@FreeBSD.org>
To:        Jim Thompson <jim@netgate.com>
Cc:        freebsd-net <freebsd-net@freebsd.org>
Subject:   Re: Intel Controllers [Rant]
Message-ID:  <7BE40656-3BF7-4D16-9E8F-392E612093D1@FreeBSD.org>
In-Reply-To: <CAKAfi7x8SJD7bCLbr2YUKK6nCQgAvZYoGiuqDfBTvweDYGwOYQ@mail.gmail.com>
References:  <1386634847.38473.YahooMailNeo@web121606.mail.ne1.yahoo.com> <1386697668.8944.57916449.7576FC53@webmail.messagingengine.com> <CAKAfi7x8SJD7bCLbr2YUKK6nCQgAvZYoGiuqDfBTvweDYGwOYQ@mail.gmail.com>

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

--Apple-Mail=_5727BAE7-DC4F-4F9B-87DB-043030333DD2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Dec 10, 2013, at 12:13, Jim Thompson <jim@netgate.com> wrote:

> On Tue, Dec 10, 2013 at 11:47 AM, Mark Felder <feld@freebsd.org> =
wrote:
>> On Mon, Dec 9, 2013, at 18:20, Barney Cordoba wrote:
>>> Why is it that every time I get a new MB it has yet-another intel
>>> controller on it? How are you supposed to write good drivers that =
support
>>> 9000 different controllers? As much as I appreciate the progression =
of
>>> CPU technology, they
>>> would serve the community better by making up their damn minds and =
just
>>> build 1 or 2 controller for each
>>> target market.
>>>=20
>>=20
>> I'm pretty sure an entirely new driver doesn't need to be written for
>> each new controller. I assume like with most things (network cards, =
wifi
>> chips, etc) it's usually a matter of adding its identifier to the =
driver
>> code.
>=20
> It goes beyond that.   In the simplest case, then yes, things are as =
you say.
>=20
> But chips have bugs, which require work-arounds, or other slightly
> strange stuff.
>=20
> Case(s) in-point:
>=20
> The 82575 assigns queues using vectors via a bitmask
> The Intel 82576 chip uses a table that essentially consists of 2
> columns with 8 rows.  The ordering is column-major (like Fortran
> arrays).
> On 82580 and newer adapters the scheme is similar to 82576, however
> instead of ordering column-major, the ordering is row-major (like C or
> Pascal).
>=20
> These chips are all supported via the igb driver.
>=20
> Some parts supported by the igb driver use MSI-X interrupts, others =
don't.
>=20
> On i350, i354, i210, and i211, loopback VLAN packets have the tag =
byte-swapped.
>=20
> The list of issues is by no means limited to the above.
>=20
> Jim

That sounds tedious. Thanks to those of you that tirelessly hack away at =
these quirks.

When I first replied to this post I thought I was reading another list =
and the discussion was about disk controllers which don't seem to be so =
troublesome



--Apple-Mail=_5727BAE7-DC4F-4F9B-87DB-043030333DD2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJSp1qaAAoJEJg7ZFAfE+JSrX0H/jg1HSvzGskZDft8HyRapXIY
zmSFuvcU879kBg+i1nSZV+TtUtIPiu0XHSkK5OmgHXa1hkoe2KXiG4UicYZI13hJ
k3xz238iZo5h7NiB7hydJxVp6gK/R7Ksnb92gu8+c8aup1kT3/GHq5g9S/AosvAi
pRkh2BpVfDpXZpCEkinqgfXA9E2UXU2hDDlxraosrCMGMXZySMIwUiFlvaCKVD5R
DqkjL2KPHsIzgtC8LrTApwcQVDeCWUTBuvDNLbyJZP71hvsCQG44xUfKydQd2ORD
5zktEGnbtRs/D3R5oThb2TckepYy6xwbnqrvLeHBP6Ia2Hd0YvLquPUBWRay26s=
=5b9e
-----END PGP SIGNATURE-----

--Apple-Mail=_5727BAE7-DC4F-4F9B-87DB-043030333DD2--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7BE40656-3BF7-4D16-9E8F-392E612093D1>