. 56122 PISA (Italy)
-+---
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net
gt;
> Thanks,
> sephe
>
> --
> Tomorrow Will Never Die
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org&q
netmap_ring).
Cheers,
Vincenzo
2017-02-16 21:58 GMT+01:00 Slawa Olhovchenkov <s...@zxy.spb.ru>:
> On Thu, Feb 16, 2017 at 09:48:14PM +0100, Vincenzo Maffione wrote:
>
> > Not sure about what you mean. Until memory areas are in use the real
> values
> > (*_num, *_size) a
hank you for any help you can provide
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffione
help you can provide
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffione
t; On Thu, Feb 16, 2017 at 09:14:19PM +0100, Vincenzo Maffione wrote:
>
> > Hi,
> > You're right, we'll try to add more details.
> >
> > In any case, buf_size, ring_size and if_size are the sizes in bytes of
> each
> > buffer, ring and netmap_if (control data
is already configurable, however.
Cheers,
Vincenzo
2017-02-14 13:36 GMT+01:00 Slawa Olhovchenkov <s...@zxy.spb.ru>:
> On Tue, Feb 14, 2017 at 12:26:55PM +0100, Vincenzo Maffione wrote:
>
> > Hi,
> > Have you tried to play with netmap sysctl parameter
cards and got the
> same results with both.
>
> Can someone help me?
>
> Thanks,
>
> David
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@f
Hi,
A change in mb_free_ext() introduced in FreeBSD 11 versions broke the
transmission support for netmap in emulated mode. This means immediate
kernel crashes for netmap users in non-native (emulated) mode.
This problem has been fixed in FreeBSD-12-CURRENT, which contains a recent
version of
checksum
> offloadings and TSO. I disabled them and everything is working perfectly
> now! Thank you so much!!
>
> On Thu, Jan 19, 2017 at 6:00 AM, Vincenzo Maffione <v.maffi...@gmail.com>
> wrote:
>
>> Hi,
>> Before answering to the question, some important d
com>:
> On 19 January 2017 at 09:11, Vincenzo Maffione wrote:
> > Hi,
> >
> > A change in mb_free_ext() introduced in FreeBSD 11 versions broke the
> > transmission support for netmap in emulated mode. This means immediate
> > kernel crashes for net
in the near future.
> It's extremely interesting and I'd love to be eraly adopter, but my
> (ESXi) setups are currently doing well and I don't have spare time or
> any business project to try out… :-(
>
Yes, it's ptnetmap. However, bhyve is going to have support for VALE ports
anyway (even
t;
>
> [http://www.stream-technologies.com/img/phone.png]
>
>
> +44 (0)844 800 8520
>
>
> |
>
>
> [http://www.stream-technologies.com/img/mouse.png]
>
>
> www.stream-technologies.com<http://www.stream-technologies.com/>
>
>
>
>
>
>
>
g list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mail
s (3 or greater)?
>
> Regards
>
> On Thu, Nov 17, 2016 at 5:11 PM, Vincenzo Maffione <v.maffi...@gmail.com>
> wrote:
>
>> Hi,
>> No, each interface open in netmap mode has its own netmap buffers (for
>> packet data) and netmap rings, independently of wh
y to find some
> time to track them down (involving LACP, VLANs, Jumbo-Frames and IPv6 –
> that was the problematic constellation)
>
> Since I have extra PHYs, I can do PCIe-passthrough like before (with
> ESXi) for some special guests. I'm looking forward to find out how this
> works with bhyve!
>
> No idea, but also ptnetmap is able to do that: not only you can
pass-through a VALE port, but also you can pass-through a physical
interface.
Cheers,
Vincenzo
> Best,
>
> -Harry
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
a
new solution for bhyve networking, which will let you attach your bhyve VMs
directly to a VALE switch, without paying additional overheads related to
TAPs, epairs, and vtnet emulation. You can find additional information,
code and performance numbers here:
https://wiki.freebsd.org/SummerOfCode2016/PtnetDriverAndDeviceModel.
nzo
>
>
> Best,
> Xiaoye
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenz
it on ethX, and packet won't end up into
the host RX ring
Of course you can play with the ring ids, to open just specific queues:
e.g. "netmap:ethX-3/T" "netmap:ethX-0/R", etc.
Cheers,
Vincenzo
> I am wondering is there a way to work around this issue.
>
&g
ufs, selected to issue
notifications to netmap applications.
The proper fix is probably to turn the macro to a function, I cannot think
of other solutions.
Cheers,
Vincenzo
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
eneric.c:765: warning: the
> address of 'generic_mbuf_destructor' will always evaluate as 'true'
> [-Waddress]
> --- netmap_generic.o ---
> *** [netmap_generic.o] Error code 1
>
> I haven’t yet dug into why this only surfaces on powe
1.5M 0 155M 0 0
> 1.5M13 0 153M 1.5M 0 153M 0 0
> 1.4M14 0 145M 1.4M 0 145M 0 0
> 1.4M17 0 151M 1.4M 0 151M 0 0
>
>
Technologies | Glasgow, UK
>
> [image: http://www.stream-technologies.com/img/phone.png]
>
> +44 (0)844 800 8520
>
> |
>
> [image: http://www.stream-technologies.com/img/mouse.png]
>
> www.stream-technologies.com
>
>
>
>
>
> --
am Technologies | Glasgow, UK
>
> [image: http://www.stream-technologies.com/img/phone.png]
>
> +44 (0)844 800 8520
>
> |
>
> [image: http://www.stream-technologies.com/img/mouse.png]
>
> www.stream-technologies.com
>
>
>
>
>
> -
go]
>
>
>
>
>
> *Steven Crangle*
>
> Systems Developer | Stream Technologies | Glasgow, UK
>
> [image: http://www.stream-technologies.com/img/phone.png]
>
> +44 (0)844 800 8520 <+44%20844%20800%208520>
>
> |
>
> [image: http://www.stream-technol
Ok, thanks for the clarification. I change the lock type to MTX_DEF
(and did a test). I attached the new patch.
Cheers,
Vincenzo
2016-12-29 2:06 GMT+01:00 John Baldwin <j...@freebsd.org>:
> On Wednesday, December 28, 2016 07:25:22 PM Vincenzo Maffione wrote:
>> Hi,
>&g
Ok! Can anyone commit this?
Luigi seems to be ok with the change.
Thanks,
Vincenzo
2016-12-29 19:16 GMT+01:00 John Baldwin <j...@freebsd.org>:
> On Thursday, December 29, 2016 10:02:32 AM Vincenzo Maffione wrote:
>> Ok, thanks for the clarification. I change the lock
for HEAD, if you wish. Just let me
know.
Cheers,
Vincenzo
2016-12-20 21:45 GMT+01:00 Adrian Chadd <adrian.ch...@gmail.com>:
> hi,
>
> What's the commit? We should get it into -HEAD asap.
>
>
> -adrian
>
>
> On 20 December 2016 at 01:25, Vincenzo Maffione <v.maffi
n
MTX_SPIN and MTX_DEF.
Cheers,
Vincenzo
2016-12-21 20:30 GMT+01:00 Luigi Rizzo <ri...@iet.unipi.it>:
> On Wed, Dec 21, 2016 at 11:15 AM, Vincenzo Maffione
> <v.maffi...@gmail.com> wrote:
>> Hi,
>> There is no commit related to that in the FreeBSD svn or git.
>&g
mit it as-is?
>> >
>> >
>> > -a
>> >
>> >
>> > On 21 December 2016 at 13:37, Vincenzo Maffione <v.maffi...@gmail.com>
>> > wrote:
>> >> Hi Luigi,
>> >> I attached a minimal change containing
xe5
> #1 0x81084d88 at witness_warn+0x3b8
> #2 0x83ef2bcc at begin_synchronized_op+0x6c
> #3 0x83f14beb at cxgbe_netmap_reg+0x5b
> #4 0x809846f1 at netmap_hw_reg+0x81
> #5 0x809806de at netmap_do_regif+0x19e
> #6 0x8098121d at netma
Ok, applied to the netmap github repo.
This fix will be published when Luigi does the next commit on FreeBSD.
Cheers,
Vincenzo
2016-12-19 20:05 GMT+01:00 Navdeep Parhar <n...@freebsd.org>:
> IFNET_RLOCK will work, thanks.
>
> Navdeep
>
> On Mon, Dec 19, 2016 at 3:21
, netmap patches just ignore VLAN tags, so that if the NIC does not
strip tags, you will see them in your netmap application.
Cheers,
Vincenzo
>
> Hope I'm not missing something obvious again, I'm about to call it a day
> here.
>
> Thanks,
>
> -harry
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
#9 0x8098624f at devfs_ioctl_f+0x13f
> #10 0x80b41b34 at kern_ioctl+0x2d4
> #11 0x80b417f1 at sys_ioctl+0x171
> #12 0x80fa26ae at amd64_syscall+0x4ce
> #13 0x80f844ab at Xfast_syscall+0xfb
>
> This is on 11.0-RELEASE-p8
>
> Thanks,
> J
de. We were using a
> pre 11 snapshot of the svn head though .
>
> Many Thanks
>
> Joe Jones
> Stream Technologies
>
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
>
without problem on the same hardware setup. I may
> try and figure out what the regression is, I'm not familiar with the
> FreeBSD release process either though.
>
> Thanks,
> Joe Jones
>
> On 24/03/17 10:29, Vincenzo Maffione wrote:
>
>> Hi Joe,
>> There wa
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
any offloading functions, since I
> don't know how it's implemented…
>
> Thanks,
>
> -harry
>
> P.S.: Still don't understand the basic difference between ./bridge and
> ./vale-ctl
>
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freeb
agg0 to vale0 = panic
> Attaching lagg0.101 to vale0 = silence
> Attaching em0.101 to vale0 = same panic as with lagg0
> Attaching em0 to vale0 = silence with tagged frames
> ifconfig em0 -vlanhwtag solves the latter, but this doesn't really
> help, because VID filtering inside
required performance (for a given workload, e.g. average
packet-size, average packet rate, etc.).
If you really want TSO an other offloadings on the phyisical NIC, then you
cannot use that NIC in netmap mode (e.g. attaching it to VALE).
Cheers,
Vincenzo
> Thanks a lot,
>
> -harry
>
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
gt;:
> On Fri, Mar 17, 2017 at 6:51 PM, Vincenzo Maffione <v.maffi...@gmail.com>
> wrote:
>
>>
>> When using your physical NICs with netmap, you need to disable the
>> offloadings because netmap is not able to program the NIC to perform these
>> offloadin
t;
But it is probably a good idea to add these example ifconfig instructions
somewhere (man page or at least the README in the netmap repo).
>
> I guess vlanhwtag, vlanhwfilter and vlanhwtso don't interfere, do they?
>
Well, I think they interfere: if you receive a tagged packet
h doesn't seem to affect anyone else than me.
>
There is an overhaul in progress, yes, but netmap support is going to be
restored.
>
> Thanks,
>
> -harry
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
ras Jha <dreadisc...@gmail.com>:
> Apologies, by KB I meant kernel bypass, since it is possible to open a
> netmap port without bypassing the kernel. I didn't know if this would
> affect it or not.
>
> On Sun, Apr 9, 2017 at 3:20 AM, Vincenzo Maffione <v.maffi...@g
__
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
Hi,
Yes, by default netmap packet buffers for all physical nics on your
machine are allocated from the same memory area. This means that you can do
zcopy with the usual swap of netmap slots.
The bridge application is an example. It does zcopy if possible, otherwise
it falls back to copying.
2PM -0700, Vincenzo Maffione wrote:
> > Sure, can anyone commit this?
>
> The addition of KASSERTs like the below one to if_handoff() and
> if_start()? Sure.
>
> Marius
>
> >
> > Il 5 lug 2017 4:05 AM, "Marius Strobl" <mar...@freebsd.org> ha scritto:
Sure, can anyone commit this?
Il 5 lug 2017 4:05 AM, "Marius Strobl" <mar...@freebsd.org> ha scritto:
> On Mon, Jul 03, 2017 at 05:08:09PM +0200, Vincenzo Maffione wrote:
> > Details here:
> >
> > https://github.com/luigirizzo/netmap/issues/322
> >
Hi,
Looks good to me, although I'm not sure whether if_transmit should
assert(mbuf == NULL). Couldn't we just drop the mbuf if we receive it?
Thanks,
Vincenzo
2017-07-18 10:43 GMT-07:00 Luiz Otavio O Souza <lists...@gmail.com>:
> On 12 July 2017 at 02:19, Vincenzo Maffione wrote
.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Bypass what?
2017-06-28 22:59 GMT-07:00 Paras Jha <dreadisc...@gmail.com>:
> It's possible to bypass this by unloading and reloading the patched
> network driver
>
> On Thu, Jun 29, 2017 at 12:39 AM, Vincenzo Maffione <v.maffi...@gmail.com>
> wrote:
>
>>
Details here:
https://github.com/luigirizzo/netmap/issues/322
Is it acceptable to commit the proposed patch?
Thanks,
Vincenzo
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any
ff8088aa5e at fork_trampoline+0xe
>
>
Yeah, the same bug jist slipped back. Discard the previous patch and
replace it with the attached one.
Cheers,
Vincenzo
> Any hints how I can get adding em0 (lagg and vlan-less) via vale-ctl
> again? (netmap_obj_malloc netmap_ring request size
No, the thing is that I misinterpreted your stack trace. The patch is ok
for a different bug. It seems that the problem are vlans more than lagg.
Which interface did you put in netmap mode, em or em.345?
Il 25 mag 2017 10:46 PM, "Harry Schmalzbauer" ha
scritto:
Bezüglich
dler
> (/usr/local/share/deploy-tools/RELENG_11/src/sys/dev/
> netmap/netmap_generic.c:628).
> 623 struct netmap_adapter *na = NA(ifp);
> 624 struct netmap_generic_adapter *gna = (struct
> netmap_generic_adapter *)na;
> 625 u_int work_done;
r": Does this mean native-netmap support
> get's lost when if_lagg(4) is in game after if_igb(4)?
>
> Thanks,
>
> -harry
>
>
>
--
Vincenzo Maffione
--- f1.c 2017-05-25 17:46:36.948871305 +0200
+++ f.c 2017-05-25 17:46:01.542203054 +0200
@@ -273,9 +273,10 @@ gene
1/src/sys/dev/netmap/
> netmap_kern.h:1254:44:
> note: expanded from macro 'NA'
> #define NA(_ifp)((struct netmap_adapter *)WNA(_ifp))
> ^
> /usr/local/share/deploy-tools/RELENG_11/src/sys/dev/netmap/
> netmap_kern.h
rstanding uninvolved vlan clones
> interfere here...
> The lagg0 does have vlan clones (lots of) defined.
> Unfortunately I can't take them out of the game for testing...
>
> Does that picture match the trace?
>
> thanks,
>
> -harry
>
>
>
--
Vin
t; it was if_lagg itself, no vlan clone.
> The latter is a completely different problem, and contrary to the
> initial panic report, vlan clones don't lead to panics anymore.
>
>
> -harry
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.or
up (memory-rootfs with additional ZFS boot and sys-pool)...
> Very complicated I am...
>
> worth the stable/11 attempt?
>
> thanks,
>
> -harry
>
>
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists
a very interisting area of optimization which is easy to
> explore with the vale:vlan scenario.
>
> In another post I described that the vale:vlan path doesn't work, while
> vale:em0 (the parent) with everything else untouched does work.
> Dou you think it's possible to fix the vale:vlan couplin
10ki/s at one igb(4) queue when
> invoked on the host, with mtu 1500.
> Same invocation in the guest, with vlan-vale setup, causes 30ki/s
> average (with high discrepancy, 20-40k).
>
> Might it be possible that if_vlan(4) influences interrupt moderation
> capabilities?
>
> Vince
,
> > traced=0) at subr_syscall.c:135
> > #14 0x808648bb in Xfast_syscall () at
> > /usr/local/share/deploy-tools/RELENG_11/src/sys/amd64/amd64/
> exception.S:396
> > #15 0x00080122813a in ?? ()
> …
> > Does anybody have a q
uestion, better addressed to virtualization@ but I remember
> cross-posting is to avoid:
> I never tried to understand why vmx3f seems to work without using
> interrupts at all, as opposed to vmx(4), but maybe it is possible to do
> the same for vtnet(4)?
>
The only way to avoid interrupts at
Il 14 giu 2017 5:21 PM, "Olivier Cochard-Labbé" ha
scritto:
On Wed, Jun 14, 2017 at 4:48 PM, John Jasen wrote:
>
> b) On the negative side, between the various releases, netmap appeared
> to be unstable with the Chelsio cards -- sometimes supported,
Hi,
To test netmap raw forwarding performance using just one core, use the
bridge program between two netmap supported NICs, like ix or ixl
# ./bridge ix0 ix1
You could implement your own multicore software router by extending the
bridge example to implement the protocols you need.
Vale-ctl
st work.
> >>
> >>
> >> It stills panic with an -head build today.
> >>
> >>
> > Fixed in r319986.
> >
> >
> > ___
> > freebsd-net@freebsd.org mailing list
> > https://
Also, there is a more basic problem. The bridge program requires physical
interfaces to be specified with the "netmap:" prefix. For example:
# ./bridge netmap:ix0 netmap:em2# OK
# ./bridge ix0 em2 # WRONG
2017-06-16 14:47 GMT+02:00 Vincenzo Maffion
nly had VF-capable hardware (actually VF-"supported" hardware,
> 82576 was SR-IOV enabled, but at the advent of 10GbE, SR-IOV support for
> older chips was removed - where initially implemented - and of course
> not implemented anywhere else).
>
> -harry
>
>
--
Vincen
72.21.34.10 is-at 00:0c:29:40:3a:dd, length 46
>
> The reply made it up to vale's uplink, but not through vale. Am I
> missing something?
> Tagging, checksum-disabling etc. seems to be right, since utilizing
> if_bridge(4) gives the expected result, but I have no idea why I can't
> get packets via vale(4).
>
> Important note: Using em0.232 parent (vlandev em0) for vale uplink does
> work!
> So I guess if_em(4)'s native netmap support interferes with the vlan clone.
> I'm out at this point, far too less knwoledge about the code paths...
> Can anybody else help here?
>
> Thanks,
>
> -harry
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
so basic setup soud be ok).
> Next idea was to utilize Open vSwitch, but that's the most painful
> solution to get vlan tags filtered (which could do the nic itself)... I
> hoped vale(4) could be utilized by Open vSwitch, but it seems that the
> ovs-n
nfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
up yesterday evening, but I'll try your
> > suggestion first. Unfortunately I don't have time to prepare a debug
>
> Since this doesn't need a reboot and I'm in adventure mood, I just tried
> it at runtime.
> Unfortunately I can't find bridge documentation besides the source co
interface
through the "bridge" program. In this way nothing changes from the
functional point of view,
but you are not attaching anymore the VLAN interface to VALE (and you are
using an additional process).
So instead of
# vale-ctl vale0:vlan0
you would have
# bridge netmap:vlan0
; to a specific core. or is there a way to know the root of such problem?
>
The only threads are the ones of your application.
Maybe your problem comes from concurrent accesses to the netmap TX ring
from different threads? Only one thread at a giv
4110,4111,16,4112,4113).
>
> So think the root of the problem is that the buffer pointer is not always
> successfully/timely updated even after the NS_BUF_CHANGED flag is set and
> the buf_idx is updated.
>
> Best,
> Xiaoye
>
>
>
> On Wed, Nov 22, 2017 at 7:39 AM, Vinc
p.github.io
>
> Jim
>
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffio
t in a slot is processed. Is there a way to move the tail
>> > pointer as long as the packet in the slot is processed? Is this a
>> > configurable feature?
>> >
>> > Best,
>> > Xiaoye
>> >
>> > On Fri, Oct 27, 2017 at 11:52 AM, Vincenzo Maffione
6 bhyve: korso (bhyve)
> …
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maf
ffering isn't a real deadlock in terms of locking, but any
> netmap-internal lockup/overflow/limit/whatever. Just guesing here! I
> don't know netmap code! I only link symptoms, and since that setup is
> working really nice for some limited time, I hoped you or any other
> netmap expert could teach me how to find the root cause.
> Your sentence about FreeBSD's netmap-interface-emulation leaves a bad
> presentiment...
>
> Thank you very much,
>
> -harry
>
--
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Hi,
With vmx driver netmap will use the emulated netmap adapter. On freebsd
netmap still does not have a way to see how many rings an interface has. So
by default will assume 1 tx/rx rings couple for emulated adapter. You can
however change this by sysctl dev.netmap.generic_rings.
Cheers,
I see, but it seems there is a bug anyway. Feel free to open a bug report
here https://github.com/luigirizzo/netmap/issues if you wish.
2017-11-07 21:13 GMT+01:00 Joe Buehler <as...@cox.net>:
> Decreasing buf_num to 32768 eliminated the allocation failure.
>
> Joe Buehler
&g
2048.
>
> Joe Buehler
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffione
___
ing incoming frames due to the vagaries of
> the LINUX kernel. Moving to the RT kernel helped, host tuning is also
> needed to eliminate large latencies in processing frames. There is good
> information on real-time KVM on the net that explains how to achieve
> what I want.
>
>
ole* lot of noise in the measurements.
>
> Joe Buehler
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffione
_
xtra buffers.
>
> Martina
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffion
nd TX rings. How do I increase this
> substantially?
>
> Joe
>
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.o
ww.interrasystems.com
>
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffione
2017-10-26 20:04 GMT+02:00 Joe Buehler <as...@cox.net>:
> Vincenzo Maffione wrote:
>
> > You can have how many threads and processes you want. The constraint is
> > that there must not be two threads accessing the same ring at the same
> > time. In this case each
You can have how many threads and processes you want. The constraint is
that there must not be two threads accessing the same ring at the same
time. In this case each pktgen is accessing different rings.
Il 26 ott 2017 7:01 PM, "Joe Buehler" <as...@cox.net> ha scritto:
> Vinc
:31 GMT+02:00 Joe Buehler <as...@cox.net>:
> Vincenzo Maffione wrote:
> > I guess you are using a FreeBSD guest. Is this the case? If you have the
>
> Sorry, I am using LINUX, ubuntu 16.04 LTS for both host and VM. I am
> posting here at standing request of netmap driver
> Best,
> Xiaoye
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
--
Vincenzo Maffione
Hello,
Can anyone please apply the attached patch? It follows up the removal of
the nkr_slot_flags in the upstream netmap.
The change fixes compilation issues and has no effect on functionality.
Thanks,
Vincenzo
--
Vincenzo Maffione
diff --git a/sys/dev/cxgbe/t4_netmap.c b/sys/dev/cxgbe
2018-01-01 23:05 GMT+01:00 Charlie Smurthwaite <charlie@atech.media>:
>
> On 01/01/18 21:05, Vincenzo Maffione wrote:
>
>
>
> 2018-01-01 17:14 GMT+01:00 Charlie Smurthwaite <charlie@atech.media>:
>
>> Hi,
>>
>> Thank you for your reply. I was abl
cal Director
>
> *tel.* *email.* charlie@atech.media *web.* https://atech.media
>
> *This e-mail has been sent by aTech Media Limited (or one of its
> assoicated group companys, Dial 9 Communications Limited or Viaduct Hosting
>
c operations are automatically performed within the
poll()/select() syscall (at least assuming you did not specify
NETMAP_NO_TX_POLL).
Also, whether netmap calls or does not call txsync/rxsync on certain rings
depends on the parameters passed to nm_open().
Make sure you check for nm_ring_space(txring) when
egistration number
> 5523199. Dial 9 Communications Limited is a UK limited company,
> registration number 7740921. Viaduct Hosting Limited is a UK limited
> company, registration number 8514362. All companies are registered at Unit
> 9 Winchester Place, North Street, Poole, Dorset, BH15 1NX.
> ___
Hi,
What you want to do is definitely possible using the "host rings", aka
"sw rings".
The idea is that netmap intercepts all the packets arriving from the NIC RX
"hardware" ring(s). Your netmap program should then look at the packets and
decide which ones should be forwarded to the host kernel
Il giorno sab 1 set 2018 alle ore 03:50 John-Mark Gurney
ha scritto:
> First, does vale work for anyone? At least one of the documented
> commands in vale(4) does not work.
>
> After manually building the netmap module and loading it:
> # tcpdump -ni vale-a:1
> 313.748851 nm_open [947] invalid
Il giorno sab 1 set 2018 alle ore 23:11 John-Mark Gurney
ha scritto:
> Vincenzo Maffione wrote this message on Sat, Sep 01, 2018 at 22:25 +0200:
> > Il giorno sab 1 set 2018 alle ore 03:50 John-Mark Gurney <
> j...@funkthat.com>
> > ha scritto:
> >
> >
1 - 100 of 151 matches
Mail list logo