Re: [PATCH 2/7] Define new syscalls readv2,preadv2,writev2,pwritev2

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

 



On Mon, Sep 15, 2014 at 04:20:37PM -0400, Milosz Tanski wrote:
> New syscalls with an extra flag argument. For now all flags except for 0 are
> not supported.

This may fall in the category of bike-shedding, and so I apologize in
advance, but I wonder if we really need readv2 and writev2 as new
syscalls.  What if we just added preadv2 and pwritev2, and implemented
readv2 and writev2 as libc wrappers where which had the vector
allocated as an automatic stack variable?  Is the extra user memory
access really going to be that noticeable?

Cheers,

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




[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