Re: [PATCH 0 of 4] Generic AIO by scheduling stacks

without linking it into the system lists. The reason I don't think this approach works (and I looked at it a few times) is that many things end up requiring special handling: things like permissions, signals, FPU state,

segment registers....

Can you share a specific example of the special handling required?

- z
-
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: [PATCH 0 of 4] Generic AIO by scheduling stacks
    • From: Benjamin LaHaise <[email protected]>

• References:
  • [PATCH 0 of 4] Generic AIO by scheduling stacks
    • From: Zach Brown <[email protected]>
  • Re: [PATCH 0 of 4] Generic AIO by scheduling stacks
    • From: Benjamin Herrenschmidt <[email protected]>
  • Re: [PATCH 0 of 4] Generic AIO by scheduling stacks
    • From: Zach Brown <[email protected]>
  • Re: [PATCH 0 of 4] Generic AIO by scheduling stacks
    • From: Benjamin LaHaise <[email protected]>

• Prev by Date: Re: Rewriting floppy.c was Re: Free Linux Driver Development!
• Next by Date: Re: remove_proc_entry and read_proc
• Previous by thread: Re: [PATCH 0 of 4] Generic AIO by scheduling stacks
• Next by thread: Re: [PATCH 0 of 4] Generic AIO by scheduling stacks
• 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]