Hi, I have a Phabricator review here that I was hoping to get some feedback
on: https://reviews.freebsd.org/D34742
In short, there's already some functionality in current and 13.1-RELEASE
that allows a driver to pick a TX queue for a packet, but this extends that
support to have iflib do some limi
know which devices need a restart /
which devices do not, or whether a restart is strictly necessary and if
there is another way to do this without worrying about restarting the
device.
- Eric
On Fri, Nov 6, 2020 at 3:35 PM mike tancsa wrote:
> On 11/6/2020 5:32 PM, Eric Joyner wrote:
> >
Could you reply to that issue with what you've found?
Though, as far as I can recall, igb(4) devices are not supposed to do
the iflib reset talked about in the bug, so I wouldn't expect to see a link
flap on those.
- Eric
On Fri, Nov 6, 2020 at 12:48 PM mike tancsa wrote:
> On 11/6/2020 2:17 P
cludes Windows/macOS fixes), so it's still
possible we'll see 8.16.6 or 8.16.7 for FreeBSD later, absent any official
messaging.
On Fri, Dec 6, 2019 at 11:08 AM Jamie Landeg-Jones
wrote:
> Eric Joyner wrote:
>
> > I'm reviving an ancient thread, but is Bullseye truly drop
I'm reviving an ancient thread, but is Bullseye truly dropping FreeBSD
support? Do you have a link to something that shows that?
I still see a FreeBSD tarball in their download archive page for the newest
version of their tool, which seems to be 8.16.5.
- Eric
On Thu, Aug 8, 2019 at 12:08 PM Ala
On Tue, Mar 19, 2019 at 5:40 AM David Chisnall wrote:
> That said, FreeBSD also runs very well under Hyper-V, so if you have
> enough RAM then you may find that a better option. In my experience,
> compilers that spawn a new process for every file (e.g. gcc, clang) are
> noticeably faster in a F
On Sun, Mar 17, 2019 at 6:35 AM Hans Petter Selasky wrote:
>
> See the freebsd-build utils package for Linux.
>
> --HPS
>
>
Is there anything for Windows?
- Eric
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/fr
ifdi_if.h is a system generated interface file that network drivers that
depend on iflib use. It's generated from ifdi_if.m in sys/net.
My guess is that you don't have "device iflib" defined in your kernel
configuration. em(4) depends on iflib in FreeBSD 12/13, and with r343617,
iflib is now expli
well as a more general update
since it looks like it's out of date). Though, there is at least a mention
of it using iflib near the bottom.
- Eric
On Fri, Feb 15, 2019 at 10:53 AM Enji Cooper wrote:
>
> > On Feb 15, 2019, at 10:46, Eric Joyner wrote:
> >
> > ifdi_if.h i
None of the Intel networking drivers on FreeBSD support Hyper-V.
Could you try "Discrete Device Assignment" instead? Create the VFs on the
host somehow, then pass them through to the VMs? That looks like it might
work for the FreeBSD VF drivers.
- Eric
On Mon, Oct 22, 2018 at 12:11 PM Michael Pr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228354
Can someone look at fixing this for 12? Non-gracefully handling long names
is a pretty bad bug.
- Eric
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freeb
Never!
On Tue, Apr 11, 2017 at 3:18 PM Sean Bruno wrote:
> ignore
>
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
^ Message ^
It takes forever, but I keep on forgetting to time how long it takes, so I
don't know how long "forever" is.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
at 2:00 PM Eric Joyner wrote:
> Ok; I will try that and will report back.
>
> - Eric
>
> On Wed, Jan 4, 2017 at 11:59 AM Konstantin Belousov
> wrote:
>
> On Wed, Jan 04, 2017 at 06:53:23PM +, Eric Joyner wrote:
> > Adding freebsd-current, because that's
Ok; I will try that and will report back.
- Eric
On Wed, Jan 4, 2017 at 11:59 AM Konstantin Belousov
wrote:
> On Wed, Jan 04, 2017 at 06:53:23PM +0000, Eric Joyner wrote:
> > Adding freebsd-current, because that's a good idea.
> >
> > I see these lines in the beginn
Eric
On Tue, Jan 3, 2017 at 11:41 PM Shane Ambler wrote:
> On 04/01/2017 08:08, Eric Joyner wrote:
> > I have an 11.0-RELEASE-p1 system with:
> >
> > hw.model: Intel(R) Xeon Phi(TM) CPU 7250 @ 1.40GHz
> >
> > It's got 68 cores, but with 4-way SMT,
Did you use the "-b" option to set the bandwidth it uses for UDP? It
defaults to 1Mb/s, which is close to what you're seeing.
Plus, I think the recommendation is that you use iperf3, anyway, and I
don't think it has this quirk.
On Thu, Sep 1, 2016 at 2:06 AM Howard Su wrote:
> I used iperf to d
d. I just
> tested with sendmail up and running then add the VF's and it still shows
> the error message.
>
> On Wed, Feb 24, 2016 at 8:04 PM, Eric Joyner wrote:
>
>> Are you still getting the -100 errors when trying to load the VF driver?
>>
>> I've t
Are you still getting the -100 errors when trying to load the VF driver?
I've tried SR-IOV on a system here, and I can confirm that traffic stops
passing on the PF interface when you create a VF interface. That didn't
used to happen, so I'm investigating why that is right now.
On Wed, Feb 24, 201
gs=143
>ifmaxaddr 0 port 1 priority 128 path cost 2000
> member: epair0a flags=143
>ifmaxaddr 0 port 5 priority 128 path cost 2000
> epair0a: flags=8943 metric
> 0 mtu 1500
> options=8
> ether -Hidden-
> inet6 fe80::ff:70ff:fe00:50a%epair0a prefixlen 64 scopeid 0x
Did you do an ifconfig up on ix1 before loading the VF driver?
On Sat, Feb 20, 2016 at 11:57 AM Ultima wrote:
> Decided to do some testing with iovctl to see how sr-iov is coming along.
> Currently when adding the vf's there are a couple errors, and the network
> no longer function after iovctl
2015 08:52:57 -0700
> Sean Bruno wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> >
> >
> > On 10/02/15 00:47, O. Hartmann wrote:
> > > On Thu, 01 Oct 2015 15:39:11 + Eric Joyner
> > > wrote:
> > >
>
Are you using IPv6?
On Thu, Nov 19, 2015 at 12:42 PM Alexander Leidinger <
alexan...@leidinger.net> wrote:
> On Wed, 11 Nov 2015 11:45:32 +0100
> Alexander Leidinger wrote:
>
> > Hi,
> >
> > I' updated a system with -current as of r287323 (end August) to
> > r290633 (yesterday).
> >
> > Result:
Oliver,
did you try Sean's suggestion?
- Eric
On Tue, Sep 22, 2015 at 1:10 PM Sean Bruno wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
>
> On 09/21/15 23:23, O. Hartmann wrote:
> > On Mon, 21 Sep 2015 21:13:18 + Eric Joyner
> > wrote
wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> >
> >
> > On 09/18/15 10:20, Eric Joyner wrote:
> > > He has an i210 -- he would want to revert e1000_i210.[ch], too.
> > >
> > > Sorry for the thrash Sean -- it so
He has an i210 -- he would want to revert e1000_i210.[ch], too.
Sorry for the thrash Sean -- it sounds like it would be a good idea for you
should revert this patch, and Jeff and I can go look at trying these shared
code updates and igb changes internally again. We at Intel really could've
done a
Or like, "taskqueue_enqueue_if_not_draining()" ? :p
On Wed, Jul 1, 2015 at 2:32 PM Konstantin Belousov
wrote:
> On Wed, Jul 01, 2015 at 05:09:27PM -0400, Ryan Stone wrote:
> > On Wed, Jul 1, 2015 at 4:58 PM, Jack Vogel wrote:
> >
> > > But if you've disabled interrupts why would an "interrupt-h
I made the change in r284767. It leaves out the backwards compatibility
ixgbe build target that the stable/10 commit allowed, but you can now build
the modules seperately.
On Mon, Jun 22, 2015 at 2:29 PM Eric Joyner wrote:
> I guess I could reverse-MFC r283668, then, to make that work on H
I guess I could reverse-MFC r283668, then, to make that work on HEAD.
On Mon, Jun 22, 2015, 12:07 PM Stefano Garzarella <
stefanogarzare...@gmail.com> wrote:
> Hi all,
> I tried to compile FreeBSD-head with only "device ix" (without "device
> ixv") but the build failed.
>
> I fixed this behavior
Let me remove my concerns earlier in the thread -- this patch won't
negatively affect any of our drivers; and the problem I mentioned with ixl
would require a change somewhere further up the stack.
---
- Eric Joyner
On Mon, Sep 8, 2014 at 5:05 AM, Rick Macklem wrote:
> Hans Petter
see if a
segment in a TSO spans more than six mbufs and then m_defrag()'s the entire
chain if one exists; it's less than optimal but necessary to prevent errors.
- Eric
---
- Eric Joyner
On Fri, Sep 5, 2014 at 11:37 AM, Hans Petter Selasky
wrote:
> Hi,
>
> I've tested
ng to look into that
performance impact, and will try to submit a patch later without one.
---
- Eric Joyner
On Wed, Feb 26, 2014 at 3:06 AM, Alexandre Martins <
alexandre.mart...@netasq.com> wrote:
> Hi Eric,
>
> In January, I have report a bug into igb driver :
>
> http:/
hanks,
---
- Eric Joyner
On Fri, Jan 10, 2014 at 02:35:29PM +0400, Gleb Smirnoff wrote:
> Yonghyeon,
>
> On Fri, Jan 10, 2014 at 10:21:14AM +0900, Yonghyeon PYUN wrote:
> Y> > I experience some troubles with the igb device driver on FreeBSD
10-RC4.
> Y> >
> Y>
33 matches
Mail list logo
