Re: stop using ioends for direct write completions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: stop using ioends for direct write completions
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 28 Jan 2016 05:16:56 -0800
Cc: darrick.wong@xxxxxxxxxx, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <1452766237-2314-1-git-send-email-hch@lst.de>
User-agent: Mutt/1.5.24 (2015-08-30)

Any chance to get a review for this?  It should really help
with sorting out the buffered I/O COW code.

_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs

Follow-Ups:
- Re: stop using ioends for direct write completions
  - From: Brian Foster
- Re: stop using ioends for direct write completions
  - From: Darrick J. Wong

References:
- stop using ioends for direct write completions
  - From: Christoph Hellwig

Prev by Date: Re: RFCv4+ WIP rollup of XFS reverse-mapping, reflink, and dedupe support
Next by Date: Re: [PATCH] xfs: split default quota limits by quota type V2
Previous by thread: [PATCH] xfs: don't use ioends for direct write completions
Next by thread: Re: stop using ioends for direct write completions
Index(es):
- Date
- Thread

[Index of Archives] [Linux XFS Devel] [Linux Filesystem Development] [Filesystem Testing] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux