public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] submount: another removeable media handler
Date: Mon, 19 May 2003 10:10:00 -0700	[thread overview]
Message-ID: <3EC90FE8.4000504@zytor.com> (raw)
In-Reply-To: <E19HiEl-000D0k-00.arvidjaar-mail-ru@f25.mail.ru>

Andrey Borzenkov wrote:
> 
>>Basically, in my opinion removable media should be handled by insert
>>and removal detection, not by access detection.  Obviously, there are
>>some sticky issues with that in the case where media can be removed
>>without notice (like PC floppies or other manual-eject devices), but
>>overall I think that is the correct approach.
> 
> 
> You are absolutely right. Unfortunately, I am not aware of any general
> way to request device to notify about media insertion/ejection.
> Without such notification the only thing you can do is to poll - and
> this is the same access detection in disguise. With disatvantage
> that polling wastes system resources and is subject to races.
> 

No, that is not correct.  Polling for insertion is different from 
probing from access.  There isn't a *general* way to obtain 
notification, but may devices offer it, so you need to develop a modular 
way to deal with it.

	-hpa


  reply	other threads:[~2003-05-19 16:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19 10:51 [ANNOUNCE] submount: another removeable media handler Andrey Borzenkov
2003-05-19 17:10 ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-17  6:05 Eugene Weiss
2003-05-16  5:06 Eugene Weiss
2003-05-16 11:33 ` Alex Riesen
2003-05-16 14:31   ` Eugene Weiss
2003-05-16 18:46     ` H. Peter Anvin
2003-05-19 16:45       ` Steve Brueggeman
2003-05-19 17:12         ` H. Peter Anvin
2003-05-16 12:16 ` Michael Buesch

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=3EC90FE8.4000504@zytor.com \
    --to=hpa@zytor.com \
    --cc=arvidjaar@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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