GitHub PushEvent at 2014-05-10 12:09:27
Repository: Blaze.Kernel-Moto-G
Actor: GuneetAtwal
Payload: {"shas":[["eab0a4c9b2677fa6a928e2d38fe562cef964abc0","c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","fs: pull iov_iter use higher up the stack\n\nRight now only callers of generic_perform_write() pack their iovec\narguments into an iov_iter structure.  All the callers higher up in the\nstack work on raw iovec arguments.\n\nThis patch introduces the use of the iov_iter abstraction higher up the\nstack.  Private generic path functions are changed to operation on\niov_iter instead of on raw iovecs.  Exported interfaces that take iovecs\nimmediately pack their arguments into an iov_iter and call into the\nshared functions.\n\nFile operation struct functions are added with iov_iter as an argument\nso that callers to the generic file system functions can specify\nabstract memory rather than iovec arrays only.\n\nAlmost all of this patch only transforms arguments and shouldn't change\nfunctionality.  The buffered read path is the exception.  We add a\nread_actor function which uses the iov_iter helper functions instead of\noperating on each individual iovec element.  This may improve\nperformance as the iov_iter helper can copy multiple iovec elements from\none mapped page cache page.\n\nAs always, the direct IO path is special.  Sadly, it may still be\ncleanest to have it work on the underlying memory structures directly\ninstead of working through the iov_iter abstraction.\n\nSigned-off-by: Dave Kleikamp <dave.kleikamp@oracle.com>\nCc: Zach Brown <zab@zabbo.net>\nmodified for Mako from LKML reference\n\nSigned-off-by: faux123 <reioux@gmail.com>","faux123",true]],"size":1,"ref":"refs/heads/kk_mr1","head":"eab0a4c9b2677fa6a928e2d38fe562cef964abc0"}