Re: [patch] aio: add per task aio wait event condition

==> On Wed, 3 Jan 2007 10:50:06 -0800, Zach Brown <[email protected]> said:

Zach> The controversial part here happens when min_nr is larger than the
Zach> ring size.  In that case I think we should consider min_nr to be
Zach> equal to the ring size.  We'll return fewer events than userspace
Zach> asked for, but it'll still be a big batch.

That sounds like a programming error, don't you think?  Maybe
returning EINVAL is the right approach?

-Jeff
-
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] aio: add per task aio wait event condition
    • From: Zach Brown <[email protected]>

• References:
  • RE: [patch] aio: add per task aio wait event condition
    • From: "Chen, Kenneth W" <[email protected]>
  • Re: [patch] aio: add per task aio wait event condition
    • From: Zach Brown <[email protected]>

• Prev by Date: Re: [PATCH 3/7] barrier: a scalable synchonisation barrier
• Next by Date: Re: [PATCH] SCSI: Add the SGPIO support for sata_nv.c
• Previous by thread: Re: [patch] aio: add per task aio wait event condition
• Next by thread: Re: [patch] aio: add per task aio wait event condition
• 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]