Re: [take25 1/6] kevent: Description.

Hans Henrik Happe wrote:

I don't know if this falls under the simplification, but wouldn't there be a race when reading/copying the event data? I guess this could be solved with an extra user index.

That's what I said, reading the value from the ring buffer structure's head would be racy. All this can only work for single threaded code.

--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-
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: [take25 1/6] kevent: Description.
    • From: Evgeniy Polyakov <[email protected]>

• References:
  • [take25 1/6] kevent: Description.
    • From: Evgeniy Polyakov <[email protected]>
  • Re: [take25 1/6] kevent: Description.
    • From: Evgeniy Polyakov <[email protected]>
  • Re: [take25 1/6] kevent: Description.
    • From: Ulrich Drepper <[email protected]>
  • Re: [take25 1/6] kevent: Description.
    • From: Hans Henrik Happe <[email protected]>

• Prev by Date: Re: [take25 1/6] kevent: Description.
• Next by Date: Re: [patch 04/19] Add a framework to manage clock event devices.
• Previous by thread: Re: [take25 1/6] kevent: Description.
• Next by thread: Re: [take25 1/6] kevent: Description.
• 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]