Colleagues,
I am experimenting with bhyve which uses tap(4) for network access.
I don't want to bridge tap0 with any of the hosts's real NICs. How can
I create a private network just between the host and the guest?
I even tried to create a lo1 interface on the host and bridge it with
tap0 but l
On Wed, Nov 04, 2015 at 01:23:42AM +0300, Andrey V. Elsukov wrote:
> On 04.11.2015 00:10, David Wolfskill wrote:
> > So... with the change from r290334, what's the point of the KASSERT?
>
> Yes, you are right. We changed this code and use it some time, but
> without INVARIANTS. I just removed this
> I have
> attached two RTT vs Time graphs for our experiments.
Oops, the list stripped my attachments, here are the images online at
https://goo.gl/photos/3oxXFvr1T1ZC88PA8 and
https://goo.gl/photos/QM1tQL157w6NRdmE6
> I have attached a graph that compares delta
> values for the two experimen
On 11/03/15 at 02:33P, Hans Petter Selasky wrote:
> On 11/03/15 14:14, Rasool Al-Saadi wrote:
> > Does anyone have thoughts on what we can test next to narrow down the
> > root-cause of these unusual timing jumps?
>
> You might also want to test the "projects/hps_head" branch, which uses a
> bit
On 04.11.2015 00:10, David Wolfskill wrote:
> So... with the change from r290334, what's the point of the KASSERT?
Yes, you are right. We changed this code and use it some time, but
without INVARIANTS. I just removed this KASSERT in r290345. Can you try
this revision? Sorry for the breakage.
--
On Tue, Nov 03, 2015 at 08:39:52AM -0800, David Wolfskill wrote:
> On Tue, Nov 03, 2015 at 06:15:35PM +0300, Alexander V. Chernikov wrote:
> > ...
> > > I tried booting it, and during the transition to multi-user mode,
> > > once ipfw was being invoked, I got the above-cited panic. Circumvention
>
On Tue, Nov 03, 2015 at 06:15:35PM +0300, Alexander V. Chernikov wrote:
> ...
> > I tried booting it, and during the transition to multi-user mode,
> > once ipfw was being invoked, I got the above-cited panic. Circumvention
> > was to leave it disconnected from a network (turn off the WiFi
> > swit
03.11.2015, 17:05, "David Wolfskill" :
> This was on my laptop; yesterday, it built & booted:
>
> FreeBSD g1-252.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #230
> r290270M/290270:1100085: Mon Nov 2 05:03:07 PST 2015
> r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64
>
> OK
This was on my laptop; yesterday, it built & booted:
FreeBSD g1-252.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #230
r290270M/290270:1100085: Mon Nov 2 05:03:07 PST 2015
r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64
OK; today, after building:
FreeBSD localhost
On 11/03/15 14:14, Rasool Al-Saadi wrote:
Does anyone have thoughts on what we can test next to narrow down the
root-cause of these unusual timing jumps?
You might also want to test the "projects/hps_head" branch, which uses a
bit different callout implementation.
--HPS
Hello all,
While we were implementing new AQMs (Codel, PIE, FQ-Codel and FQ-PIE) in
FreeBSD targeting ipfw+Dummynet, we noticed timing issue with Dummynet when we
increase kernel timer interrupt Hz (changing the value of kern.hz in
/boot/loader.conf) to 3000 or higher. The issue is that spikes
11 matches
Mail list logo