clawsoon@yahoo.com wrote:
> Any idea what might be going on here?
>
> Any idea how to fix it?

I remember when installing a GigE card in an Origin200 that there
was something one was supposed to do with systune to enhance
the kernel parameters for operation of the GigE port. Did you do
that? Can't remember what the changes are now, but they should
be detailed in the GigE installation guide on techpubs.

Cheers!

Ian.

PS. Irony: if you had IRIX/IRIX transmission, Origin can sustain
980Mbit/sec, though it does need good CPUs to do this...

In article <1159379026.339660.48760@i42g2000cwa.googlegroups.c om>,
wrote:

>clawsoon@yahoo.com wrote:
>> Any idea what might be going on here?

>> Any idea how to fix it?

>I remember when installing a GigE card in an Origin200 that there
>was something one was supposed to do with systune to enhance
>the kernel parameters for operation of the GigE port.

There's a configuration utility for the gige card; I don't recall it's
name at the moment.

>Did you do
>that? Can't remember what the changes are now, but they should
>be detailed in the GigE installation guide on techpubs.

>PS. Irony: if you had IRIX/IRIX transmission, Origin can sustain
>980Mbit/sec, though it does need good CPUs to do this...

We had terrible performance between Novell and an O3000 gigE
even though the link was only running at 100 Mb. 3 or 4 packets
[speaking literally] would get transmitted, the 200 ms timer would
have to fire before the O3000 would send the ACKs. We had to switch
that link to a 100 Mb card and that solved the problem. It wasn't
a problem with that particular gigE card: we swapped and the problem
persisted.

>>>>> "WR" == Walter Roberson writes:

WR> There's a configuration utility for the gige card; I don't recall it's
WR> name at the moment.

egconfig for Tigon2 based cards
tgconfig for Tigon3 based cards

tg2 was a dog.

max

Max Matveev wrote:
>>>>>> "WR" == Walter Roberson writes:

> WR> There's a configuration utility for the gige card; I don't recall it's
> WR> name at the moment.

> egconfig for Tigon2 based cards
> tgconfig for Tigon3 based cards

> tg2 was a dog.

Certainly, it had very high DMA setup latencies, which meant that its
aggregate small packet performance was rather limited - in netperf
TCP_RR terms to something on the order of 40K Transactions per
second. (Well, on the HP 9000's I benchmarked anyway

It also meant that the NIC could not hit link-rate on bulk transfer
with a 1500 byte MTU if the packets were in more than one buffer per.
That meant it usually went faster on a netperf TCP_STREAM test than a
netperf TCP_SENDFILE test - on HP-UX at least the data copies were
such that the TCP segments were single-buffer, with room left for the
link-level headers.

The perils of having a CPU on the NIC's datapath...

rick jones
--
denial, anger, bargaining, depression, acceptance, rebirth...
where do you want to be today?
these opinions are mine, all mine; HP might not want them anyway...
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...

Max Matveev wrote:
> >>>>> "WR" == Walter Roberson writes:
>
> WR> There's a configuration utility for the gige card; I don't recall it's
> WR> name at the moment.
>
> egconfig for Tigon2 based cards
> tgconfig for Tigon3 based cards
>
> tg2 was a dog.
>
> max

Thanks! I looked through lots of SGI docs and found tgconfig mentioned
everywhere, but I didn't hear about egconfig anywhere. I'm accessing
the card with it now, dumping some stats... nothing meaningful yet,
since I just started playing with it about five minutes ago.

It says the card is an Alteon AceNIC v6. How would that compare to a
Tigon3 based card, performance-wise?

Andrew Klaassen