Re: MTU not regrowing?

Andrea Venturoli wrote this message on Tue, Jun 24, 2014 at 20:43 +0200: > Today I experienced something weird (at least for me) on a 8.4 system: > > _ the system had vlan3 interface, with default MTU (1500 bytes); > _ "ping -D -s 1400 somehost" would work, but "ping -D -s 1500 somehost" > would

Re: MTU not regrowing?

Hi-- On Jun 24, 2014, at 11:43 AM, Andrea Venturoli wrote: > Hello. > > Today I experienced something weird (at least for me) on a 8.4 system: > > _ the system had vlan3 interface, with default MTU (1500 bytes); > _ "ping -D -s 1400 somehost" would work, but "ping -D -s 1500 somehost" would >

[Bug 190785] [em] cpu affinity not working in FreeBSD 10-STABLE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785 --- Comment #10 from gon...@bsdinfo.com.br --- Cool Thanks! Works now. :D Cheers, -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailin

[Bug 190785] [em] cpu affinity not working in FreeBSD 10-STABLE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785 --- Comment #9 from John Baldwin --- Ah, the "em0 que" thread is a separate helper thread created by the em driver to service a taskqueue. It is not an interrupt thread so it is not affected by 'cpuset -x'. However, you can use 'procstat

[Bug 190785] [em] cpu affinity not working in FreeBSD 10-STABLE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785 --- Comment #8 from gon...@bsdinfo.com.br --- Yes it changes the CPU. With top -PSH you can see it changing CPU. I did: cpuset -x 264 -l 3 See my top below: PID USERNAME PRI NICE SIZERES STATE C TIMEWCPU COMMAND 10 r

[Bug 190785] [em] cpu affinity not working in FreeBSD 10-STABLE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785 John Baldwin changed: What|Removed |Added Status|Needs Triage|Issue Resolved Resolution|-

Re: Ordering problem in if_detach_internal regarding if_bridge

On Monday, June 23, 2014 1:12:54 pm Roger Pau Monné wrote: > On 23/06/14 18:49, Alexander V. Chernikov wrote: > > On 23.06.2014 20:39, Alexander V. Chernikov wrote: > >> On 23.06.2014 19:32, John Baldwin wrote: > >>> On Friday, June 20, 2014 11:25:51 am Roger Pau Monné wrote: > Hello, > >

Re: MTU not regrowing?

On 06/24/14 21:03, John Hay wrote: Do a "route get somehost" and see what mtu is returned. You might be able to delete or tweak that route. Thanks a lot! I learned something new :) I'll try this next time I have the chance. bye av. ___ free

Re: MTU not regrowing?

On Tue, Jun 24, 2014 at 08:43:28PM +0200, Andrea Venturoli wrote: > Hello. > > Today I experienced something weird (at least for me) on a 8.4 system: > > _ the system had vlan3 interface, with default MTU (1500 bytes); > _ "ping -D -s 1400 somehost" would work, but "ping -D -s 1500 somehost" > w

Re: MTU not regrowing?

On Tue, Jun 24, 2014 at 11:43 AM, Andrea Venturoli wrote: > _ the system had vlan3 interface, with default MTU (1500 bytes); > _ "ping -D -s 1400 somehost" would work, but "ping -D -s 1500 somehost" > would yield "frag needed and DF set" (forgive me if the message is not > exact, I don't have it

Re: MTU not regrowing?

don't forget the header of the ping. the -s flag specifies the amount of data that the ping carries. By specifying a size of 500, you are creating a ping packet larger than the MTU. On 24 June 2014 19:43, Andrea Venturoli wrote: > Hello. > > Today I experienced something weird (at least for me)

MTU not regrowing?

Hello. Today I experienced something weird (at least for me) on a 8.4 system: _ the system had vlan3 interface, with default MTU (1500 bytes); _ "ping -D -s 1400 somehost" would work, but "ping -D -s 1500 somehost" would yield "frag needed and DF set" (forgive me if the message is not exact, I

[Bug 190785] [em] cpu affinity not working in FreeBSD 10-STABLE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785 --- Comment #6 from gon...@bsdinfo.com.br --- So it's not a bug, it's a feature of the driver. Can we close this bug then. Thanks and best regards -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 190785] [em] cpu affinity not working in FreeBSD 10-STABLE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190785 --- Comment #5 from John Baldwin --- Well, cpuset -x forces affinity for the ithread even if the driver did not request it. I do believe that em does not request specific affinity on its own. -- You are receiving this mail because: You a

[Bug 181657] [bpf] [patch] BPF_COP/BPF_COPX instruction reservation (sync with NetBSD)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181657 Christian Brueffer changed: What|Removed |Added CC||bruef...@freebsd.org

Re: [zone: Mbuf_cluster] kern.ipc.nmbclusters limit reached in Virtual machine causes downtime

On Tue, Jun 24, 2014 at 2:53 AM, Stefan Stere wrote: > Hi, > > I have a vmware virtual server running FreeBSD 10.0 STABLE > The virtual server has 100mbps port. > > It is running a Tor router, consuming an average of 6-7 TB of monthly > traffic. Its the only purpose of the server. > > Last night

Re: ifaddr refcount problem

On Tue, Jun 24, 2014 at 3:08 AM, Gleb Smirnoff wrote: > On Mon, Jun 23, 2014 at 10:44:58AM -0600, Alan Somers wrote: > A> > On Fri, Jun 20, 2014 at 12:15:21PM -0700, Navdeep Parhar wrote: > A> > N> Revision 264905 and 266860 that followed it seem to leak ifaddr > A> > N> references. ifa_ifwithdst

Re: ifaddr refcount problem

On Mon, Jun 23, 2014 at 10:44:58AM -0600, Alan Somers wrote: A> > On Fri, Jun 20, 2014 at 12:15:21PM -0700, Navdeep Parhar wrote: A> > N> Revision 264905 and 266860 that followed it seem to leak ifaddr A> > N> references. ifa_ifwithdstaddr and ifa_ifwithnet both install a A> > N> reference on the

[zone: Mbuf_cluster] kern.ipc.nmbclusters limit reached in Virtual machine causes downtime

Hi, I have a vmware virtual server running FreeBSD 10.0 STABLE The virtual server has 100mbps port. It is running a Tor router, consuming an average of 6-7 TB of monthly traffic. Its the only purpose of the server. Last night it went down, and vmware console log was saying: [zone: Mbuf_cluster]