Re: netmap/vale periodic deadlock

2017-11-21 Thread Harry Schmalzbauer
Bezüglich Vincenzo Maffione's Nachricht vom 21.11.2017 09:39 (localtime): … > > If this is the case, although you are allowed to do that, I don't think > it's a convenient way to use netmap. > Since VLAN interfaces like vlan0 do not have (and cannot have) native > netmap support, you are falling b

Re: BPF packet pagesize limit

2017-11-21 Thread Ryan Stone
Do not allocate MJUM9BYTES clusters under any circumstances. Trying to allocate them when the system is under memory pressure is enormously expensive and stands a good chance of livelocking the system if you try to allocate too many too quickly, even when allocating with M_NOWAIT. Honestly, suppo

Re: BPF packet pagesize limit

2017-11-21 Thread Kristof Provost
On 21 Nov 2017, at 17:14, Catalin Salgau wrote: Actually m_getm2() will always produce a chain for a size larger than the page size, due to m_getjcl() being called with MJUMPAGESIZE every time a large buffer is requested. The function could probably be called with MJUM9BYTES in this case, but t

Re: BPF packet pagesize limit

2017-11-21 Thread Catalin Salgau
On 20/11/2017 11:26 pm, Kristof Provost wrote: > On 19 Nov 2017, at 19:49, Catalin Salgau wrote: > > I'm trying to address the limitation in (upstream) net/vblade that was > brought up in > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205164 > This is related to writes large

Re: netmap/vale periodic deadlock

2017-11-21 Thread Harry Schmalzbauer
Bezüglich Vincenzo Maffione's Nachricht vom 21.11.2017 14:26 (localtime): > It may be that your is not a deadlock but some kind of crash. Enabling > debugging features would probably help (e.g. to get a stack trace). > Maybe your lockup/crash happened because you did some reconfiguration > (ring si

Re: netmap/vale periodic deadlock

2017-11-21 Thread Vincenzo Maffione
It may be that your is not a deadlock but some kind of crash. Enabling debugging features would probably help (e.g. to get a stack trace). Maybe your lockup/crash happened because you did some reconfiguration (ring size, number of rings, etc.) while netmap was active and doing so you triggered some

王鑫焱邀请您加入领英

2017-11-21 Thread 王鑫焱 via freebsd-net
王鑫焱邀请您加入全球领先的职业社交网站 LinkedIn (领英)。领英能帮助您管理职业生涯，让您接触到全球各地的工作机会。 快来加入领英，创建您的职业档案，轻松拓展职场人脉！ 王鑫焱 深圳市华融凯科技有限公司 - 总经理 中国 广东 深圳 接受邀请: https://www.linkedin.com/comm/start/accept-invitation?sharedKey=kdBMJXHW&invitationId=6338700858955530248&trk=eml-china-m2g-a-cta&trkEmail=eml-invite_guest-null-31-null

Re: netmap/vale periodic deadlock

2017-11-21 Thread Harry Schmalzbauer
Bezüglich Vincenzo Maffione's Nachricht vom 21.11.2017 09:39 (localtime): > Hi, > It's hard to say, specially because it happens after two days of > normal use. > Can't you enable deadlock debugging features in your kernel? > https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/k

[Bug 223767] tun device allows modification of if_type to any value causing a page fault and panic

2017-11-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223767 Hans Petter Selasky changed: What|Removed |Added CC||hsela...@freebsd.org --- Com

Re: netmap/vale periodic deadlock

2017-11-21 Thread Vincenzo Maffione
Hi, It's hard to say, specially because it happens after two days of normal use. Can't you enable deadlock debugging features in your kernel? https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html However, if I understand correctly you have created some

Re: local_unbound, resolvconf, vpn

2017-11-21 Thread Dag-Erling Smørgrav
Alexander Zagrebin writes: > Also I have to notice that there is another issue with the default > local_unbound setup: > by default unbound uses syslog for logging, but usually the > local_unbound service starts before syslogd and so logging doesn't work > until local_unbound will be reloaded. Th