Re: [Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-20 Thread Martin Birgmeier
20 Jan 2019, Martin Birgmeier wrote: > >> Regarding duplex, ifconfig shows the following: >> >> [0]# ifconfig em0 >> em0: flags=8843 metric 0 mtu >> 1500 >>     >> options=81249b >> >>     ether f0:de:f1:98:86:a9 >>   

Re: [Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-20 Thread Martin Birgmeier
to be o.k. -- Martin On 20.01.19 06:28, Bruce Evans wrote: > On Sat, 19 Jan 2019, Martin Birgmeier wrote: > >> I just tried the patch by Bruce (from the mail sent 10 hours ago), but >> it makes no difference. >> >> Also, it does not seem like bad frames or too high an int

Re: [Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-20 Thread Martin Birgmeier
I am not using resume at all... just normal startup/shutdown. -- Martin On 20.01.19 07:19, Bruce Evans wrote: > On Sun, 20 Jan 2019, Bruce Evans wrote: > >> [iflib_media_change() is missing iflib_stop(), like iflib_resume() was] >> >> I don't know what the media was after the broken resume.  Its

Re: [Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-19 Thread Martin Birgmeier
I just tried the patch by Bruce (from the mail sent 10 hours ago), but it makes no difference. Also, it does not seem like bad frames or too high an interrupt rate are the problem (the machine should easily handle what is coming from its NFS client which only has a 100 Mbps interface). I believe

Re: Tying down network interfaces

2014-12-31 Thread Martin Birgmeier
/freebsd-questions/2009-January/190453.html , http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190624.html -- Martin On 12/30/14 21:13, Freddie Cash wrote: On Dec 30, 2014 10:02 AM, Martin Birgmeier la5lb...@aon.at mailto:la5lb...@aon.at wrote: Hi, I have two network

Tying down network interfaces

2014-12-30 Thread Martin Birgmeier
Hi, I have two network interfaces as follows: sis0: NatSemi DP8381[56] 10/100BaseTX port 0xa400-0xa4ff mem 0xd580-0xd5800fff irq 9 at device 9.0 on pci0 sis1: NatSemi DP8381[56] 10/100BaseTX port 0x9400-0x94ff mem 0xd480-0xd4800fff irq 11 at device 12.0 on pci0 When sis0 breaks down,

Re: amd + NFS reconnect = ICMP storm + unkillable process.

2011-08-27 Thread Martin Birgmeier
Thank you for these patches. One interesting thing: I was trying to backport them to 7.4.0 and RELENG_7, too, but there the portion of the code dealing with the RPC_CANTSEND case does not exist. On the other hand, the problem surfaced (for me) when upgrading from 7.4 to 8.2. So could one

Re: amd + NFS reconnect = ICMP storm + unkillable process.

2011-07-06 Thread Martin Birgmeier
Hi Artem, I have exactly the same problem as you are describing below, also with quite a number of amd mounts. In addition to the scenario you describe, another way this happens here is when downloading a file via firefox to a directory currently open in dolphin (KDE file manager). This will

Vote in favor of keeping ATM (was: NATM still scheduled for removal - please follow up to keep it in-tree)

2011-02-19 Thread Martin Birgmeier
now I was not subscribed to freebsd-net. -- Martin Birgmeier Vienna Austria ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org

Locking in ng_tty.c

2011-02-19 Thread Martin Birgmeier
In ng_tty.c, function ngt_newhook(), there is the following code: if (sc-hook) return (EISCONN); NGTLOCK(sc); sc-hook = hook; NGTUNLOCK(sc); I do not think this is proper - should not the test be within the lock? Regards, Martin -- Martin