Thread (1 message) 1 message, 1 author, 2012-03-20

Re: [PATCH] process_vm_{read,write}v(3): initial man pages

From: Mike Frysinger <hidden>
Date: 2012-03-20 00:50:47

On Monday 19 March 2012 16:45:41 Michael Kerrisk (man-pages) wrote:
A quick question about one piece:
quoted
+The count values might be individually capped according to
\fIUIO_MAXIOV\fP. +If the Linux kernel is capped at smaller values, the
C library will take care +of emulating the limit it exposes (if it is
bigger) so the user only needs to +care about that (what the C library
defines).
I don't see anything in glibc that does this. Have I missed something?
i think you're correct.  the code in glibc atm is merely a syscall().  i think 
the idea was to have the C library guarantee that and if moving forward the 
kernel changes, the C library would update by adding a wrapper.  maybe just 
drop this sentence until that day comes ?
-mike

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help