Re: slow open() calls and o_nonblock

On Mon, 2007-06-04 at 10:20 -0400, Aaron Wiebe wrote:
> I understand, but this is exactly the situation that I'm complaining
> about.  There is no functionality to provide a nonblocking open - no
> ability to come back around and retry a given open call.

So exactly how would you expect a nonblocking open to work? Should it be
starting I/O? What if that involves blocking? How would you know when to
try again?

  Trond

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: slow open() calls and o_nonblock
    • From: "Aaron Wiebe" <[email protected]>

• References:
  • slow open() calls and o_nonblock
    • From: "Aaron Wiebe" <[email protected]>
  • Re: slow open() calls and o_nonblock
    • From: "Aaron Wiebe" <[email protected]>

• Prev by Date: Re: lid switch hangs notebook
• Next by Date: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
• Previous by thread: Re: slow open() calls and o_nonblock
• Next by thread: Re: slow open() calls and o_nonblock
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]