public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: root@chaos.analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: poll
Date: Thu, 17 Jun 2004 19:24:07 -0700	[thread overview]
Message-ID: <40D25247.3050509@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0406171958570.3414@chaos>

Richard B. Johnson wrote:
> On Thu, 17 Jun 2004, Ben Greear wrote:
> 
> 
>>Richard B. Johnson wrote:
>>
>>>Hello,
>>>Is it okay to use the 'extra' bits in the poll return value for
>>>something? In other words, is the kernel going to allow a user-space
>>>program to define some poll-bits that it waits for, these bits
>>>having been used in the driver?
>>
>>Can't you just do a read and determine from the results of the read
>>what you actually got?  If not, add framing to your message so that
>>you *CAN* determine one message type from another...
>>
>>Ben
>>
> 
> 
> The mailbox read(s) is/are 32-bit int(s). There is no way to identify
> it as being "new" or something that was written two weeks ago.
> That's why we use poll. Poll says 'I got something new for you'.

Then use 3 different file descriptors to poll/read.  That seems more
efficient anyway as it doesn't wake the folks who don't care.

Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  parent reply	other threads:[~2004-06-18  2:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 14:05 poll Richard B. Johnson
2004-06-17 22:34 ` poll Ben Greear
2004-06-18  0:19   ` poll Richard B. Johnson
2004-06-18  0:32     ` poll Davide Libenzi
2004-06-18  0:42       ` poll Richard B. Johnson
2004-06-18  2:24     ` Ben Greear [this message]
2004-06-18 11:22       ` poll Richard B. Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40D25247.3050509@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox