Re: [PATCH 1/3] Vectorize aio_read/aio_write methods

 	do {
-		ret = file->f_op->aio_read(iocb, iocb->ki_buf,
-			iocb->ki_left, iocb->ki_pos);
+		struct iovec iov = {
+			.iov_base = iocb->ki_buf,
+			.iov_len = iocb->ki_left
+		};
+
+		ret = file->f_op->aio_read(iocb, &iov, 1, iocb->ki_pos);

this still has the lifetime problems Ben pointed out.  aio might still
be outstanding when this thread returned to userspace, so we need to
dynamically allocated the iovec and free it later.  (or make it part
of the iocb?)

-
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 1/3] Vectorize aio_read/aio_write methods
    • From: Badari Pulavarty <[email protected]>

• References:
  • [PATCH 0/3] VFS changes to collapse all the vectored and AIO support
    • From: Badari Pulavarty <[email protected]>
  • [PATCH 1/3] Vectorize aio_read/aio_write methods
    • From: Badari Pulavarty <[email protected]>

• Prev by Date: Re: [PATCH 1/3] s390: dasd extended error reporting module.
• Next by Date: Re: Linux 2.6.15.2
• Previous by thread: [PATCH 1/3] Vectorize aio_read/aio_write methods
• Next by thread: Re: [PATCH 1/3] Vectorize aio_read/aio_write methods
• 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]