Date: Mon, 26 Oct 2015 21:52:25 -0500 From: Adrian Chadd <adrian.chadd@gmail.com> To: "Pokala, Ravi" <rpokala@panasas.com> Cc: "freebsd-geom@freebsd.org" <freebsd-geom@freebsd.org>, "freebsd-scsi@freebsd.org" <freebsd-scsi@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, "ken@freebsd.org" <ken@freebsd.org>, "imp@freebsd.org" <imp@freebsd.org>, "scottl@freebsd.org" <scottl@freebsd.org> Subject: Re: Low-level trace-buffers in CAM Message-ID: <CAJ-Vmo=cfvA5k5rQt=KHpuCypHn2%2BfqYm8gBiG5eMYspBwfuNw@mail.gmail.com> In-Reply-To: <A760883F-317D-46C9-AD7C-B8F5D96A49DA@panasas.com> References: <A760883F-317D-46C9-AD7C-B8F5D96A49DA@panasas.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, ok. So this is where I create work for people. :-) Something I've been tossing up for quite some time is a generic version of this that exposes a ring-buffer of entries back to userland. For things like this, things like ALQ/KTR, etc, it's all just a producer-consumer ring based thing. You don't even care about multiple readers; that's a userland thing. So, I'm a big fan of this. I did this for the ath driver to debug descriptors and register accesses and it was a big help. I'd really like to see a more generic way we can expose this data in an efficient manner! -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=cfvA5k5rQt=KHpuCypHn2%2BfqYm8gBiG5eMYspBwfuNw>