> If I had to wager a guess as to what's going on, I'd say that when
> you start the system, the wsmouse0 gets attached to wsmux2 when the
> system comes up, but by the time you unplug the mouse and plug it in
> again, your application has the /dev/wsmouse0 device open, [...]
The application opens
hello. I think a clue lies in a snippet of the wsmux(4) man page:
If a wskbd(4), wsbell(4), or wsmouse(4) device is opened despite having a
mux it will be detached from the mux.
If I had to wager a guess as to what's going on, I'd say that when you
start the system,
th
> How are you forcing the mouse to use mux 2? [...]
Custom kernel, with "mux 2" specified on the relevant attachment lines.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39
hello. Silly question. How are you forcing the mouse to use mux 2?
Is it a custom
kernel, a sysctl variable, an unused mouse plugged into the machine elsewhere?
-thanks
-Brian
I'm working on a turnkey product under 9.1. Among other things, it
uses X for output and for keyboard input, but reads mouse input events
semi-directly (mostly because it wants deltas, whereas X insists on
integrating deltas into absolute locations, then clipping those
locations to the screen limi
Chuck Silvers writes:
> in the longer term, I think it would be good to use even larger pool pages
> for large pool objects on systems that have relatively large amount of memory.
> even with your patch, a 1k pool object on a system with a 4k VM page size
> still has 33% overhead for the redzone
On Tue, Feb 23, 2021 at 06:25:50PM +1100, matthew green wrote:
> hi folks.
>
>
> while we were debugging some memory starvation issues i noticed that
> the "kmem-02048" pool only has 1 item per page on a system with 4KiB
> pages, same similarly "kmem-04096" on 8KiB page systems. i assume
> this
m...@eterna.com.au (matthew green) writes:
>while we were debugging some memory starvation issues i noticed that
>the "kmem-02048" pool only has 1 item per page on a system with 4KiB
>pages, same similarly "kmem-04096" on 8KiB page systems. i assume
>this also occurs on 16KiB page systems for the
