Regarding latency of Netmap i/o

2018-07-01 Thread Suneet Singh
Dear Professor, I am Suneet from India. I am a PhD student in Unicamp, Campinas, Brazil. I am testing latency of MACSAD P4 software switch. I found that latency using netmap i/o is higher than using socket_mmap i/o while in case of dpdk, latency is very low. As I read the research papers related

Problem reports for n...@freebsd.org that need special attention

2018-07-01 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 229404] [pflog] [pfsync] [patch] pflogs/pfsync kernel modules build fails with VIMAGE

2018-07-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229404 Kristof Provost changed: What|Removed |Added Assignee|p...@freebsd.org |k...@freebsd.org S

[Bug 229404] [pflog] [pfsync] [patch] pflogs/pfsync kernel modules build fails with VIMAGE

2018-07-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229404 --- Comment #4 from commit-h...@freebsd.org --- A commit references this bug: Author: kp Date: Sun Jul 1 18:09:17 UTC 2018 New revision: 335847 URL: https://svnweb.freebsd.org/changeset/base/335847 Log: pflog/pfsync: Fix module build wi

Re: IPv6 scope handling, was Re: svn commit: r335806 - projects/pnfs-planb-server/usr.sbin/nfsd

2018-07-01 Thread Rick Macklem
Andrey V. Elsukov wrote: [stuff snipped] >> >> I think what you are saying above is that a Link-local address won't work >> and that the address must be a global one? >> Should the code check for "fe8" at the start and skip over those ones? > >It is possible that all hosts are in the same scope zon

Re: IPv6 scope handling, was Re: svn commit: r335806 - projects/pnfs-planb-server/usr.sbin/nfsd

2018-07-01 Thread Andrey V. Elsukov
On 01.07.2018 03:30, Rick Macklem via freebsd-net wrote: >> [neighbor1 fe80::100]<-->[fe80::1%igb0 | fe80::1%igb1]<-->[fe80::100 >> neighbor2] >> >> neighbor1 can not reach neighbor2, since these addresses belongs to >> different scope zones. On the host with two interfaces you as user can >> use l

[Bug 229432] 11.2 network em driver - connection link flaps with dhcient and option 26 (interface mtu)

2018-07-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229432 Eugene Grosbein changed: What|Removed |Added Summary|11.2 network em driver -|11.2 network em driver -

[Bug 229432] 11.2 network em driver - connection link flaps with dhclient and option 26 (interface mtu)

2018-07-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229432 Eugene Grosbein changed: What|Removed |Added Summary|11.2 network em driver -|11.2 network em driver -

[Bug 229432] 11.2 network em driver - connection link flaps

2018-07-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229432 --- Comment #4 from Eugene Grosbein --- Created attachment 194808 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=194808&action=edit proposed fix for dhclient Here is proposed patch that makes dhclient verify if new MTU differs f