LaoTsao (Dr. Tsao) wrote:
> hi
> what is the timeline for ce to be support in crossbow?
>
there is no timeline.
ce is not a gldv3 device. it would first have to be updated to be one.
then there would be the effort to convert it to crossbow.
the owners of the ce driver code have not been willing to make any
forward looking statements about ce and gldv3. it isn't even clear to
me at this point that they will ever do it. i'm still trying to get a
word one or the other from them... if they aren't doing a ce gldv3 port,
then i may revive my shelved effort. (adding ce support for crossbow
would be fairly easy once the much harder task of updating it for gldv3
is done. however, updating it for gldv3 will have a negative
performance impact under some workloads unless we can also get soft-lso
integrated. i believe roamer lu is working on soft-lso.)
-- garrett (who has a dodgy shift key)
> TIA
>
> David Edmondson wrote:
>
>> On Thu, Sep 13, 2007 at 02:18:37PM +0100, Tony Marshall wrote:
>>
>>
>>> However after I have configured the zone with the ip-type=exclusive
>>> setting in update 4 and removed the address portion of the net
>>> configuration for the zone however it does not configure the
>>> physical interface in the zone. The error message I receive is
>>> "WARNING: unable to hold network interface 'ce101000' .: Invalid
>>> argument" Looking through sunsolve there is nothing that I can see
>>> there.
>>>
>>>
>> The NIC that you assign to the zone must be one with a GLDv3
>> driver. ce is not such.
>>
>> dme.
>> _______________________________________________
>> crossbow-discuss mailing list
>> crossbow-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss
>>
>>
> _______________________________________________
> crossbow-discuss mailing list
> crossbow-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss
>
