Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1159799 > unrolled thread
| Started by | Ming Lei <ming.lei@canonical.com> |
|---|---|
| First post | 2015-06-06 02:50 +0200 |
| Last post | 2015-06-06 02:50 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v4 1/5] fs: kiocb: introduce IOCB_DONT_DIRTY_PAGE flag for direct IO Ming Lei <ming.lei@canonical.com> - 2015-06-06 02:50 +0200
| From | Ming Lei <ming.lei@canonical.com> |
|---|---|
| Date | 2015-06-06 02:50 +0200 |
| Subject | Re: [PATCH v4 1/5] fs: kiocb: introduce IOCB_DONT_DIRTY_PAGE flag for direct IO |
| Message-ID | <pyatc-vK-7@gated-at.bofh.it> |
On Fri, Jun 5, 2015 at 11:03 PM, Christoph Hellwig <hch@infradead.org> wrote: > As mentioned last time a big fat NAK for this one. We generally > do not dirty kernel pages anywhere, so a flag that must alway be set > for default behavior just to prepare for a highy hypothetical user that > in the future might want to abuse the interface is a no-go. > > Just make the dirtying behavior dependent on the iov_iter type: > dirty for ITER_IOVEC and do nothing for ITER_KVEC and ITER_BVEC. Both ITER_KVEC and ITER_BVEC doesn't mean the pages are kernel page, for example of loop and swap. That is why this patch is more flexiable, and won't cause regression since the users may have different dirtying rules as you mentioned last time. http://marc.info/?t=143093223200001&r=1&w=2 Thanks, Ming -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web