On Sun, Jan 27 2019 10:37:52 -0500, Ted Unangst wrote:
> Ingo Schwarze wrote:
> > If people here agree with the general direction of making -S the
> > default and removing the fragile non-S mode (see the patch below),
> > i'll run a full make build and make release and then ask for OKs.
>
> Just c
Hi Scott,
Scott Cheloha wrote on Tue, Feb 05, 2019 at 12:02:39AM -0600:
> Oof, folks I think we've missed the forest for the trees here.
>
> By focussing on the minutiae of the Latin translation we've discarded
> the English motto ("through to the stars") that imho
> anchored the whole thing.
>
We have iterated on various designs to reduce pressure on kmem map over time.
One of the problems is that sometimes you want to allocate something in intr
context (NOWAIT), and other times in process context (WAITOK), but then at
free time they get all glommed together. This happens in pool.
Since
When using anchors, they ought to have a non-empty name or none at all.
By accident, I discovered the following:
$ printf 'anchor ""\n' | pfctl -vnf-
pass all no state
No errors and it parses in a potentially harmful way. Other use cases
behave badly as well:
$ printf '
Hi!
Going to end and begging of buffer doesn't set marks in Emacs.
Index: basic.c
===
RCS file: /cvs/src/usr.bin/mg/basic.c,v
retrieving revision 1.47
diff -u -p -u -p -r1.47 basic.c
--- basic.c 10 Oct 2015 09:13:14 - 1.
Hi Ted,
Ted Unangst wrote on Sun, Jan 27, 2019 at 10:37:52AM -0500:
> Ingo Schwarze wrote:
>> If people here agree with the general direction of making -S the
>> default and removing the fragile non-S mode (see the patch below),
>> i'll run a full make build and make release and then ask for OKs.
When an isochronous transfer of n frames is scheduled, the last frame
i.e. frame number (n - 1) is set to generate an interrupt.
To figure out which transfer generated the interrupt, the interrupt
handler iterates over all outstanding transfers and checks if the last
TD of the transfer is active.
