Re: [RFC 0/5] dio: clean up completion phase of direct_io_worker()

> code more maintainable (I hope/wish we could also do something similar with
> simplifying the locking as well).

I agree, and that is definitely on my medium-term todo list.

> Of course with this code, we have to await rigorous testing
> ... and more reviews, but please consider this as my ack for the approach.

Yeah, absolutely.  Is there a chance that IBM can throw some testing
cycles at it?  I have it queued up for some moderately sized DB runs
over here (FC arrays, cable pulling, that kind of thing.)

- 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/

---

• References:
  • [RFC 0/5] dio: clean up completion phase of direct_io_worker()
    • From: Zach Brown <[email protected]>
  • Re: [RFC 0/5] dio: clean up completion phase of direct_io_worker()
    • From: Suparna Bhattacharya <[email protected]>

• Prev by Date: Re: Access Control Lists for tmpfs
• Next by Date: Re: [RFC][PATCH] set_page_buffer_dirty should skip unmapped buffers
• Previous by thread: Re: [RFC 0/5] dio: clean up completion phase of direct_io_worker()
• Next by thread: Re: [RFC 0/5] dio: clean up completion phase of direct_io_worker()
• 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]