linux-kernel - Re: [RFC] Simple userspace interface for PCI drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060831001742.GB26265@kroah.com>
Date:	Wed, 30 Aug 2006 17:17:42 -0700
From:	Greg KH <greg@...ah.com>
To:	Manu Abraham <abraham.manu@...il.com>
Cc:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Andrew de Quincey <adq_dvb@...skialf.net>
Subject: Re: [RFC] Simple userspace interface for PCI drivers

On Thu, Aug 31, 2006 at 02:50:55AM +0400, Manu Abraham wrote:
> Greg KH wrote:
> > On Wed, Aug 30, 2006 at 09:07:44PM +0400, Manu Abraham wrote:
> >> Being a bit excited and it is really interesting to have such a
> >> proposal, it would simplify the matters that held us up even more,
> >> probably. The name sounds fine though. All i was wondering whether there
> >> would be any high latencies for the same using in such a context. But
> >> since the transfers would occur in any way, even with a kernel mode
> >> driver, i think it should be pretty much fine.
> > 
> > As mentioned, this framework is being used in industrial settings right
> > now, where latencies are a huge issue.  It works just fine, so I do not
> > think there are any problems in this area.
> 
> Cool.
> 
> Is there some way we can avoid the poll ? It would be a real gain
> indeed, if a POLL can be avoided.

Use the signal that will be sent to your userspace program when an
interrupt happens.

If you can handle the small latency that causes it should be fine, but
if you can't, then you should be using poll :)

It all depends on the hardware you are using, your processor, and what
your tolerances are on your interrupt handling latency.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/