[brussels-dev] Re: [networking-discuss] Brussels high-level design document

[sowmini.varadhan at sun.com]

On (06/20/07 10:39), Erik Nordmark wrote:
>
>> However, given that driver.conf is used for non-network driver parameters
>> as well, I don't think driver.conf itself can be completely eradicated
>> even if it is somewhat clumsy to use. Brussels will, at least, provide
>> a cleaner method for  network drivers.
>
> I don't think it helps at all in the diskless case, which is why I suspect 
> that most of the networking driver knobs in driver.conf will remain.
>
> If the customer needs some workaround (e.g., turn of autonegotation of 
> speed; force 100 Mbps) or some performance tweak (e.g., enable jumboframes) 
> they can do that in the driver.conf on the server which serves up the root 
> file system/boot archive.
>
> *If* and only if you can have the Brussels properties apply when the driver 
> is attached then you have a way to avoid driver.conf settings for 
> networking drivers.

Brussels properties will be available when the driver attaches: early on 
in the xxx_attach routine, each converted driver will invoke dladmd with 
a door_upcall and persistent properties will be loaded up in the kernel
for the driver as part of the door_upcall. So this should work equivalent
to the driver.conf behavior for diskless client.

--Sowmini