Re: bpf_mtap_softint

[Martin Husemann <martin%duskware.de@localhost>]

On Wed, Jan 18, 2017 at 04:48:32PM +0900, Ryota Ozaki wrote:
> Note that it of course consumes more CPU time for softint
> and more memory for m_dup. That said, I think that this is
> a suitable workaround for now until someone makes them
> softint-based.

Could you provide some TODO like document (e.g. on the wiki) where
the poor soul wading into ISDN drivers (i.e.) could find out what
exactly needs to be done to the drivers? (Even if this is just two
or three sentences, it should be spelled out explicitly.)

Did I understand correctly that you will add the defered mtap to all
drivers for now, and after the driver has been fixed it will return to
old bpf_mtap? So if we ask nxr for users of the defered tap and find none,
we know that the task is done?

Martin