this is basically pair(4) except at layer 3 instead of Ethernet.
i have a few reasons for this.
pair basically exists to move packets between rdomains, which are a
layer 3 construct. pushing an ethernet header onto an mbuf data payload
and then pulling it off again on the other side of the link
On Sun, Jan 08, 2023 at 09:15:04PM -0300, Crystal Kolipe wrote:
> I've just had a casual look through all of the rasops code, including
> rasops2.c which has been moved to the attic, and I can't see where these
> values are used.
Seems like the only use was in rasops24.c and this use was removed
On Sun, Jan 08, 2023 at 03:09:44PM -0500, Dave Voutila wrote:
>
> Philip Guenther writes:
>
> > On Sat, Jan 7, 2023 at 11:04 AM Dave Voutila wrote:
> >
> > Bringing this to tech@ to increase my chance of someone testing my
> > diff.
> >
> > As reported in this thread on misc@ [1], I believe
On Sun, Jan 08, 2023 at 07:20:46PM -0500, Scott Cheloha wrote:
> On Sun, Jan 08, 2023 at 03:09:44PM -0500, Dave Voutila wrote:
> >
> > Philip Guenther writes:
> >
> > > On Sat, Jan 7, 2023 at 11:04 AM Dave Voutila wrote:
> > >
> > > Bringing this to tech@ to increase my chance of someone
On Sun, Jan 08, 2023 at 03:09:44PM -0500, Dave Voutila wrote:
>
> Philip Guenther writes:
>
> > On Sat, Jan 7, 2023 at 11:04 AM Dave Voutila wrote:
> >
> > Bringing this to tech@ to increase my chance of someone testing my
> > diff.
> >
> > As reported in this thread on misc@ [1], I believe
On Sun, Jan 08, 2023 at 10:34:23PM +, Nicholas Marriott wrote:
> > > - Why do you change RS_SCROLLBACK_SCREENS?
> >
> > To more closely mirror xterm behaviour. The current scrollback buffer is a
> > tiny fraction of what xterm offers by default. It's not that important,
> > but
> > if we're
Good news!
I have tested this revision in a T4-2 LDOM with help from kn@. Booted
the patched kernel, built a release, booted the resulting bsd.rd,
upgraded, booted into the upgrade kernel. The whole cycle. It all
worked.
In this revision I believe I am *now* using send_softint() correctly,
Reply inline.
On Sun, 8 Jan 2023 at 21:38, Crystal Kolipe
wrote:
> On Sun, Jan 08, 2023 at 08:55:46PM +, Nicholas Marriott wrote:
> > This is still too big for one go so I think it needs split further. I
> > suggest that first we get three diffs with the very easy stuff:
> >
> > 1) The two
On Fri, Dec 30 2022, Miod Vallat wrote:
>> I'm not sure which way to go: either sprinkle some -fno-common between
>> crunchgen and distrib/special/Makefile.inc, or drop -dc on lld archs
>> only. What would you folks prefer?
>
> I'd rather have the same behaviour for all platforms, but I need to
On Sun, Jan 08, 2023 at 08:55:46PM +, Nicholas Marriott wrote:
> This is still too big for one go so I think it needs split further. I
> suggest that first we get three diffs with the very easy stuff:
>
> 1) The two bug fixes
>
> 2) HPA/VPA/INDN/RIN
You didn't mention '3' :-)
But anyway,
This is still too big for one go so I think it needs split further. I
suggest that first we get three diffs with the very easy stuff:
1) The two bug fixes
2) HPA/VPA/INDN/RIN
Some other comments on the larger diff:
- Why do you change RS_SCROLLBACK_SCREENS?
- Wouldn't it be better to make
Philip Guenther writes:
> On Sat, Jan 7, 2023 at 11:04 AM Dave Voutila wrote:
>
> Bringing this to tech@ to increase my chance of someone testing my
> diff.
>
> As reported in this thread on misc@ [1], I believe newer Intel hardware
> may be experiencing issues hosting Linux guests under
On Sat, Jan 7, 2023 at 11:04 AM Dave Voutila wrote:
> Bringing this to tech@ to increase my chance of someone testing my
> diff.
>
> As reported in this thread on misc@ [1], I believe newer Intel hardware
> may be experiencing issues hosting Linux guests under vmm/vmd. It looks
> like there are
On Sun, Jan 8, 2023 at 8:50 AM Dave Voutila wrote:
> Now that guenther@ landed thread names, this should help users
> understand vmd host cpu utilization better as it lets us distinguish
> between the libevent thread and the vcpu thread.
>
> Example ps output:
>
> $ ps -AHf | grep vmd
> 30584
Now that guenther@ landed thread names, this should help users
understand vmd host cpu utilization better as it lets us distinguish
between the libevent thread and the vcpu thread.
Example ps output:
$ ps -AHf | grep vmd
30584 502984 p2 S+p 0:00.76 | |-- obj/vmd -d
46975 512305 ?? Sc
15 matches
Mail list logo
