Re: [PATCH 4/5] iomap: implement direct I/O

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

To: Avi Kivity <avi@xxxxxxxxxxxx>
Subject: Re: [PATCH 4/5] iomap: implement direct I/O
From: Christoph Hellwig <hch@xxxxxx>
Date: Sun, 6 Nov 2016 17:36:01 +0100
Cc: Christoph Hellwig <hch@xxxxxx>, linux-xfs@xxxxxxxxxxxxxxx, axboe@xxxxxx, kent.overstreet@xxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx
In-reply-to: <2dabe3ec-193b-3ecf-af5c-a5ba976de6eb@scylladb.com>
User-agent: Mutt/1.5.17 (2007-11-01)

> Does this include support for more than one concurrent appending write for 
> the same file?

No.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

References:
- an iomap-based direct I/O implementation V2
  - From: Christoph Hellwig
- [PATCH 4/5] iomap: implement direct I/O
  - From: Christoph Hellwig
- Re: [PATCH 4/5] iomap: implement direct I/O
  - From: Avi Kivity

Prev by Date: Re: When is export_operations.get_parent triggered?
Next by Date: Re: [RFC 0/6] vfs: Add timestamp range check support
Previous by thread: Re: [PATCH 4/5] iomap: implement direct I/O
Next by thread: Re: [PATCH 4/5] iomap: implement direct I/O
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux