The following reply was made to PR kern/138620; it has been noted by GNATS.
From: dfil...@freebsd.org (dfilter service)
To: bug-follo...@freebsd.org
Cc:
Subject: Re: kern/138620: commit references a PR
Date: Thu, 3 May 2012 01:41:22 + (UTC)
Author: emaste
Date: Thu May 3 01:41:12 2012
Synopsis: [lagg] [patch] lagg port bpf-writes blocked
State-Changed-From-To: open->patched
State-Changed-By: emaste
State-Changed-When: Thu May 3 01:41:29 UTC 2012
State-Changed-Why:
Committed revision 234936.
http://www.freebsd.org/cgi/query-pr.cgi?pr=138620
Hi,
On Wed, May 2, 2012 at 5:52 PM, Steven Atreju wrote:
> Luigi Rizzo wrote:
>> 2. apparently, bcopy is not the fastest way to copy memory.
>
> http://now.cs.berkeley.edu/Td/bcopy.html
>
"Pentium 166, Triton Chipset, EDO memory"... ahem.
- Arnaud
> Best Regards.
>
> Steven.
>
It's highly chipset and processor dependent what works best. Intel now
has non-temporal loads and stores which work much better in some cases
but provide little benefit in others.
-Kip
On Wed, May 2, 2012 at 11:52 PM, Steven Atreju wrote:
> Luigi Rizzo wrote:
>> 2. apparently, bcopy is not the f
Luigi Rizzo wrote:
> 2. apparently, bcopy is not the fastest way to copy memory.
http://now.cs.berkeley.edu/Td/bcopy.html
Best Regards.
Steven.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscrib
Hi all,
I have some questions regarding accomplishing the strong model for
ingress IPv6 traffic with FreeBSD, as implemented in ip6_input.c.
Does it make sense to have a strong ES model in IPv6 *at all*? I’ve
yet to find any wording in the RFC’s referring to this – although
nothing explicitly di
