Hi,
On 2015-12-10, at 20:42, Denis Pearson wrote:
> I can probably find out a snapshot with the code at the time and extract a
> diff, yes. I just don't know how it worths wasting the time when the problem
> is not reproducible on the current 1.4.8 driver which will hopefully get into
> -CURRE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205194
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202484
--- Comment #1 from oliv...@cochard.me ---
errno(2) translate error number 45 by a EOPNOTSUPP.
And code in netinet/ip_mroute.c can return EOPNOTSUPP in 2 cases:
if ((vifcp->vifc_flags & VIFF_TUNNEL) != 0) {
CTR1(KTR_IPMF, "%s: tunnels
[snip]
If RSS works fine on the latest driver then great.
This was with single queue netperf, right?
-a
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsub
On Thu, Dec 10, 2015 at 10:58:11AM -0500, James Craig wrote:
>
>
> Hey all!
>
> I am migrating some of our services to freeBSD, and in the process of this,
> I have discovered something that seems odd to me; netgroups don't seem to work
> as expected.
>
> I am trying to set up a machine that wi
On Wed, Dec 09, 2015 at 11:45:46AM +0300, Andrey V. Elsukov wrote:
> On 08.12.15 08:32, Jason wrote:
> > Hi,
> >
> > It appears the IPv6 router advertisement code paths were written fairly
> > lockless, assuming you would never process multiples concurrently. We
> > are seeing multiple page fault
On Thu, Dec 10, 2015 at 4:40 PM, Adrian Chadd
wrote:
> On 10 December 2015 at 10:29, Denis Pearson
> wrote:
> > On Thu, Dec 10, 2015 at 2:18 PM, Eggert, Lars wrote:
> >
> >> On 2015-10-26, at 18:40, Eggert, Lars wrote:
> >> > On 2015-10-26, at 17:08, Pieper, Jeffrey E <
> jeffrey.e.pie...@inte
Hey there,
I rebuild my box (FreeBSD 10.2R amd64) with netmap support.
Just to check if everything going well, I connected my laptop to another
machine in same ip range.
The problem is when I issue "tcpdump -i netmap:re0" command to capture
packets, I see different results but all of them will fai
On Thu, Dec 10, 2015 at 10:40 AM, Adrian Chadd wrote:
> On 10 December 2015 at 10:29, Denis Pearson wrote:
>> On Thu, Dec 10, 2015 at 2:18 PM, Eggert, Lars wrote:
>>
>>> On 2015-10-26, at 18:40, Eggert, Lars wrote:
>>> > On 2015-10-26, at 17:08, Pieper, Jeffrey E
>>> wrote:
>>> >> As a caveat,
On 10 December 2015 at 10:29, Denis Pearson wrote:
> On Thu, Dec 10, 2015 at 2:18 PM, Eggert, Lars wrote:
>
>> On 2015-10-26, at 18:40, Eggert, Lars wrote:
>> > On 2015-10-26, at 17:08, Pieper, Jeffrey E
>> wrote:
>> >> As a caveat, this was using default netperf message sizes.
>> >
>> > I get
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205165
Sean Bruno changed:
What|Removed |Added
Assignee|freebsd-net@FreeBSD.org |sbr...@freebsd.org
--- Comment #2 fro
On Thu, Dec 10, 2015 at 2:18 PM, Eggert, Lars wrote:
> On 2015-10-26, at 18:40, Eggert, Lars wrote:
> > On 2015-10-26, at 17:08, Pieper, Jeffrey E
> wrote:
> >> As a caveat, this was using default netperf message sizes.
> >
> > I get the same ~3 Gb/s with the default netperf sizes and driver 1.
On 2015-10-26, at 18:40, Eggert, Lars wrote:
> On 2015-10-26, at 17:08, Pieper, Jeffrey E wrote:
>> As a caveat, this was using default netperf message sizes.
>
> I get the same ~3 Gb/s with the default netperf sizes and driver 1.4.5.
Now there is version 1.4.8 on the Intel website, but it does
Hey all!
I am migrating some of our services to freeBSD, and in the process of this,
I have discovered something that seems odd to me; netgroups don't seem to work
as expected.
I am trying to set up a machine that will eventually be a file server
(running 10.2-RELEASE) and getent netgroup do
On 12/10/15 16:35, Randall Stewart wrote:
If you did that it would change the KPI a bit meaning lots
of thrashing in the code.
Hi,
There are only 5 consumers of the callout_reset() return code in the
FreeBSD 11-current kernel from what I can see:
grep -r "= callout_reset" sys/ | wc -l
On 12/10/15 16:25, Randall Stewart wrote:
For callout_stop/drain you get
-1 == Callout as already gone off or is not running (usually the latter) else
the caller iks
not using locking properly or did not lock and check the active()
value (which would have returned not active so no s
If you did that it would change the KPI a bit meaning lots
of thrashing in the code.
And on top of that you now would no longer return 0..
You would get 1 it was restarted or -1 it was not running but is now started.
Makes no sense to me sorry..
R
On Dec 10, 2015, at 7:35 AM, Hans Petter Selask
For callout_stop/drain you get
-1 == Callout as already gone off or is not running (usually the latter) else
the caller iks
not using locking properly or did not lock and check the active()
value (which would have returned not active so no stop
would have been needed);
0 == w
Hans:
Though it would not hurt to add your patch, its not possible
for callout_reset() to return anything but 1 or 0.
Only callout_stop(), callout_drain(), callout_async_drain() can return -1.
So I don’t think that this will fix it.
R
On Dec 4, 2015, at 11:34 AM, Hans Petter Selasky wrote:
>>
Hi,
Here is the backtrace for a reproducable panic seen with arptimer():
#0 doadump (textdump=0) at pcpu.h:221
#1 0x80385afb in db_dump (dummy=, dummy2=false,
dummy3=0, dummy4=0x0) at /usr/img/freebsd/sys/ddb/db_command.c:533
#2 0x803858ee in db_command (cmd_table=0x0) at
/
20 matches
Mail list logo
