le for stable/11,
> whereas on stable/12 ixgbe is served by iflib, and therefore
> we need a different patch.
>
> I'll keep you updated then.
>
> Cheers,
> Vincenzo
>
> Il giorno mer 5 dic 2018 alle ore 20:45 Andrew Vylegzhanin <
> avv...@gmail.com> ha scritt
the one node I can copy 1GB file, and after NFS hang on file with size 30 k
>чт, 1 нояб. 2018 г. в 04:46, Andrew Vylegzhanin :
>> чт, 1 нояб. 2018 г. в 3:27, Rick Macklem :
>>
>>Also need to test setup with infniband set from connected mode to
datagram mode.
Tests for datagram
gainst FreeBSD-HEAD) to to support jumbo frames in
> ixgbe.
> https://reviews.freebsd.org/D18402
> Would you be able to test it?
>
> Thanks,
> Vincenzo
>
> Il giorno gio 22 nov 2018 alle ore 13:37 Andrew Vylegzhanin <
> avv...@gmail.com> ha scritto:
>
>&
rs,
> Vincenzo
>
WBR,
--
Andrew
> Il giorno gio 22 nov 2018 alle ore 11:23 Andrew Vylegzhanin <
avv...@gmail.com> ha scritto:
>>
>> Hi,
>>
>> Come back to subject after two years.
>> I would like to clarify situation with jumbo frames in ixgbe drive
Hi,
Come back to subject after two years.
I would like to clarify situation with jumbo frames in ixgbe driver.
I've looked to
https://github.com/luigirizzo/netmap/blob/master/LINUX/ixgbe_netmap_linux.h
and see a lot of changes compared 11/12-STABLE version ixgbe_netmap.h.
Is it possible to back p
2017-05-18 12:38 GMT+03:00 Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net>:
>
> This is a long standing issue with VMware ESXi, it effects
> Linux as well as FreeBSD and Windows. A couple of googles
> for things like
>
https://www.google.com/search?q=esxi+guest+ethernet++order&ie=utf-8&oe=
2017-05-18 15:43 GMT+03:00 Gary Palmer :
>
> Out of curiosity, if you install sysutils/dmidecode from ports and
> run
>
> dmidecode -t 41
>
> does it help at all?
This table is empty on VM:
[root@freebsd11-template ~]# dmidecode -t 41
# dmidecode 3.0
Scanning /dev/mem for entry point.
SMBIOS 2.4
3"
ethernet0.pciSlotNumber = "192"
ethernet1.pciSlotNumber = "224"
ethernet2.pciSlotNumber = "256"
ethernet3.pciSlotNumber = "1184" <== vmx0 !!!
2017-05-18 6:52 GMT+03:00 Ryan Stone :
>
> On Wed, May 17, 2017 at 7:32 PM, Andrew Vylegzhanin
wrote:
Ok, but probably interface renumbering was not checked in those bug.
Here is similar topic https://forum.pfsense.org/index.php?topic=95621.0
Here is pciconf:
[root@freebsd11-template ~]# pciconf -lv
hostb0@pci0:0:0:0: class=0x06 card=0x197615ad chip=0x71908086 rev=0x01
hdr=0x00
vendor
Hi!
Recently I found a bug with numbering four (and probably more) vmxnet3
interfaces under ESXi 6.5 (FreeBSD 11.0-RELASE, 10.0-RELEASE and ESXi 5.5U1
reproduced).
It seems that this is an old bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198406 :
>
Just reproduced this bug on ESXi 6.
About week ago I've patched if_ix.c, just returned back code fragment of
max_frame_size determination from 2.8.3 version of ixgbe driver:
/*
** Determine the correct mbuf pool
** for doing jumbo frames
*/
if (adapter->max_frame_size <= 2048)
problem is that over time physical memory becomes fragmented and
> eventually 9K of contiguous memory can't be allocated anymore. This is why
> many drivers now limit themselves to page-sized clusters.
>
> On Mon, Jun 6, 2016 at 10:03 AM, Luigi Rizzo wrote:
>
>> On Mon,
Hello all,
I have an application that uses netmap for capture jumbo frames. The frames
are fixed size and have fixed rate (for example size 5166, rate 5 pps).
The frames are pure Ethernet, without IP header.
Everything works fine in 10.0-RELEASE, 10.1-RELEASE.
Starting from 10.3 and actua
13 matches
Mail list logo
