Sorry for the delay; it looked fine to me, but I never got back to you.
- Eric
On Mon, Jul 13, 2015 at 3:16 PM Adrian Chadd wrote:
> Hi,
>
> It's fine by me. Please do it!
>
>
> -a
>
>
> On 13 July 2015 at 13:05, hiren panchasara wrote:
> > Here is the patch I'd like to push which exposes 32bi
Hi,
It's fine by me. Please do it!
-a
On 13 July 2015 at 13:05, hiren panchasara wrote:
> Here is the patch I'd like to push which exposes 32bit RSS has that we
> get from ixgbe cards irrespective of whether RSS is defined or not.
>
> https://people.freebsd.org/~hiren/patches/ix_expose_rss_ha
Here is the patch I'd like to push which exposes 32bit RSS has that we
get from ixgbe cards irrespective of whether RSS is defined or not.
https://people.freebsd.org/~hiren/patches/ix_expose_rss_hash.patch
This is similar to what we've done for igb(4): r281838
In this patch I am also proposing t
Karl Pielorz wrote this message on Mon, Jul 13, 2015 at 09:33 +0100:
> --On 10 July 2015 11:06 -0700 John-Mark Gurney wrote:
>
> > Try bumping the MTU on the root em's by 4 (1504) before creating the
> > lagg...
>
> I had thought of that - but didn't want to try it (on the basis that out of
> a
--On 13 July 2015 13:06 +0100 Gary Palmer wrote:
Have you read the HARDWARE section of vlan(4)?
Kind of cryptic answer ;) - But I just read vlan(4). So it looks like my
understanding of vlans (i.e. 'long frames' as it calls them) was right?
On supported kit - creating a sub interface on a
On Mon, Jul 13, 2015 at 10:29:48AM +0100, Karl Pielorz wrote:
>
>
> --On 13 July 2015 10:51 +0200 Steve Read wrote:
>
> > Think about what it means. The MTU on the lagg0 interface is the
> > largest packet it can send for you or for its VLAN interfaces. The MTU
> > on the lagg0.10 (VLAN) inte
Hi.
How can I configure VLAN priority on FreeBSD10-STABLE or FreeBSD11-CURRENT?
Thanks,
Alex.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@free
--On 13 July 2015 10:51 +0200 Steve Read wrote:
Think about what it means. The MTU on the lagg0 interface is the
largest packet it can send for you or for its VLAN interfaces. The MTU
on the lagg0.10 (VLAN) interface is the largest packet *it* can send for
you. The VLAN tag is added to the
Thanks. I’ve added it to my todo list. (No promises about when I’ll have time
though.)
Regards,
Kristof
> On 13 Jul 2015, at 11:11, Alexey Pereklad wrote:
>
> Hi.
>
> I checked if I can reproduce this issue with -CURRENT. Well, -CURRENT has the
> same problem. Here is my test lab:
>
> # una
Hi.
I checked if I can reproduce this issue with -CURRENT. Well, -CURRENT
has the same problem. Here is my test lab:
# uname -a
FreeBSD test-BSD-01.hyperv.local 11.0-CURRENT FreeBSD 11.0-CURRENT #1
r285351: Fri Jul 10 14:49:08 MSK 2015
root@test-BSD-01.hyperv.local:/usr/obj/usr/src/sys/GENER
On 10.07.2015 15:04, Karl Pielorz wrote:
>
> The MTU on lagg0.10 has shrunk by 4 (size of VLAN tag). Is there a way
> of avoiding that?
No.
Think about what it means. The MTU on the lagg0 interface is the
largest packet it can send for you or for its VLAN interfaces. The MTU
on the lagg0.10 (VLA
--On 10 July 2015 11:06 -0700 John-Mark Gurney wrote:
Try bumping the MTU on the root em's by 4 (1504) before creating the
lagg...
I had thought of that - but didn't want to try it (on the basis that out of
all the other example config's I've seen - no one else has to, and it will
break th
12 matches
Mail list logo
