Hi Stephen,
On Mon, Oct 28, 2019 at 09:42:53AM -0700, Stephen Hemminger wrote:
(...)
> > I'd see an API more or less like this :
> >
> > int ioport(int op, u16 port, long val, long *ret);
> >
> > would take values such as INB,INW,INL to fill *, OUTB,OUTW,OUL
> > to read from , possibly ORB,OR
Hi Andy,
On Thu, Oct 24, 2019 at 09:45:56PM -0700, Andy Lutomirski wrote:
> Hi all-
>
> Supporting iopl() in the Linux kernel is becoming a maintainability
> problem. As far as I know, DPDK is the only major modern user of
> iopl().
>
> After doing some research, DPDK uses direct io port access
On Fri, Oct 25, 2019 at 07:45:47AM -0700, Andy Lutomirski wrote:
> But, for uses like DPDK, /sys/.../resource0 seems like a *far* better
> API, since it actually uses the kernel's concept of which io range
> corresponds to which device instead of hoping that the mappings don't
> change out from und
3 matches
Mail list logo
