I am sure that I have ever heard a better word for programming than
Entwicklung
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Peter
Linnell
Sent: Wednesday, August 07, 2013 5:53 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket
I am sure that I have NOT ever heard a better word for programming than
Entwicklung
-Original Message-
From: Dean, David (I/S)
Sent: Thursday, August 08, 2013 9:11 AM
To: 'Linux on 390 Port'
Subject: RE: TX-Errs on hipersocket interface.
I am sure that I have ever heard a better word
Hi all,
I will not be at SHARE in Boston, there will be some new faces who are new to
mainframe from SUSE SE team. I know you folks will treat them kindly :)
That said the real reason for S.u.S.E is related to a former law in Germany
which required a company's name to reflect what they did.
From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Carsten
Otte [co...@de.ibm.com] Sent: Thursday, July 25, 2013 7:53 AM To:
LINUX-390@VM.MARIST.EDU Subject: Re: TX-Errs on hipersocket interface.
Alan wrote:
Carsten, this is information
On 2 August 2013 13:45, Billy R. Bingham brbing...@stx.rr.com wrote:
I for one would like to know. :) You don't have
to post to the list, you can email me private,
or if you perfer you can post a URL where I can
read about it.
Right! Did someone miss the fact that it's Friday? First thing
, 2013 7:53 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.
Alan wrote:
Carsten, this is information that really needs to be in the Device Driver
book, as it differs from the traditional interpretation of TX/RX counters.
Ah, you're right - that would be accouned as dropped
...@linux.vnet.ibm.com]
Sent: Friday, July 26, 2013 3:05 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.
Jon,
without any performance data my answer can be only vague. But let's
assume a performance increase for data sending when moving from SLES10
to SLES11. If the receiver has
: TX-Errs on hipersocket interface.
Ron,
Carsten's first explanation is correct. If you see tx_errors on a
HiperSockets interface, it usually means transmission of a packet fails
because the receiver has currently no free receive buffer. You should
verify first if the receiver has configured
www.baldor.com
From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Ursula Braun
[ubr...@linux.vnet.ibm.com]
Sent: Friday, July 26, 2013 3:05 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.
Jon,
without any
,
390 Port cc
linux-...@vm.mar
ist.edu Subject
TX-Errs on hipersocket interface.
24.07.2013 22:13
Please respond
On Thursday, 07/25/2013 at 02:58 EDT, Carsten Otte co...@de.ibm.com
wrote:
TX errors on a Hipersocket are business as usual. When the receiver
fails
to pick up packets at the same rate that the transmitter transmits, the
queues will run full over time. TCP uses packet loss as a measure to
tune
Alan wrote:
Carsten, this is information that really needs to be in the Device Driver
book, as it differs from the traditional interpretation of TX/RX counters.
Ah, you're right - that would be accouned as dropped, not TX error. Forget
about my
reply then, time to look at other causes for that TX
...@de.ibm.com]
Sent: Thursday, July 25, 2013 7:53 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.
Alan wrote:
Carsten, this is information that really needs to be in the Device Driver
book, as it differs from the traditional interpretation of TX/RX counters.
Ah, you're right
Address:rfos...@baldor.com
www.baldor.com
From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Carsten Otte
[co...@de.ibm.com]
Sent: Thursday, July 25, 2013 7:53 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface
-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ursula
Braun
Sent: Thursday, July 25, 2013 9:54 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.
Ron,
Carsten's first explanation is correct. If you see tx_errors on a
HiperSockets interface
From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Carsten Otte
[co...@de.ibm.com]
Sent: Thursday, July 25, 2013 7:53 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.
Alan wrote:
Carsten, this is information that really needs to be in the Device
Ron,
See page 11 of this presentation:
http://www.vm.ibm.com/service/vmreqzeh.html
This presentation is found on
http://www.ibm.com/developerworks/linux/linux390/perf/tuning_networking.htmlwhere
there are other good tuning tips.
On Thu, Jul 25, 2013 at 2:42 PM, Ron Foster
Hello,
While investigating another problem, I did a netstat -I on our production SAP
Linux App Servers.
To my surprise, I am getting TX-ERRS on a hipersocket interface on two of our
systems. The two systems have recently been converted to SLES11 SP2. The
hipersocket device is connected
18 matches
Mail list logo
