diff for duplicates of <87a7rm3eb5.fsf@xmission.com> diff --git a/a/1.txt b/N1/1.txt index be849fd..9e1c113 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -66,7 +66,7 @@ call arguments with seccomp. Which most of the time is a pretty big downside. -From what I have seen the only truly interesting case for extending +>From what I have seen the only truly interesting case for extending waitid is something file descriptor based so the parent/child relationship is not necessary to wait for a process to terminate. diff --git a/a/content_digest b/N1/content_digest index c49e1ca..a547942 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -95,7 +95,7 @@ "downside.\n" "\n" "\n" - "From what I have seen the only truly interesting case for extending\n" + ">From what I have seen the only truly interesting case for extending\n" "waitid is something file descriptor based so the parent/child\n" "relationship is not necessary to wait for a process to terminate.\n" "\n" @@ -114,4 +114,4 @@ "\n" Eric -94e59ef0c372a8ca121d8c9e28df123a97766d15c8545840e3d03dae7f3b6034 +17dd404f391c7ed9dabba704aaf54dd1bcfe224c15ea7a347c04a748144d31aa
diff --git a/a/1.txt b/N2/1.txt index be849fd..f0a9f23 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -64,23 +64,3 @@ at all. The trouble with attributes is that means you can't filter your system call arguments with seccomp. Which most of the time is a pretty big downside. - - -From what I have seen the only truly interesting case for extending -waitid is something file descriptor based so the parent/child -relationship is not necessary to wait for a process to terminate. - -As for getrusage. If a sane union of the rusage limits and cgroups or -something like cgroups could be devised. That would be ideal. Of -course except for the memory cgroups the similarity to the resource -usage measurments and limits really isn't there. So I don't know if -merging them would be a real possibility. - -So I suspect the simplest thing to do would be to set a flag in the -idtype member of waitid that says give me rusage64 and then we would -be done. Alternately we could use the low bits of the resource usage -pointer. Assuming we don't want to introduce another syscall that is. -I really don't see much incremental extensibility potential in the wait -or rusage interface right now. - -Eric diff --git a/a/content_digest b/N2/content_digest index c49e1ca..bea0947 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -92,26 +92,6 @@ "\n" "The trouble with attributes is that means you can't filter your system\n" "call arguments with seccomp. Which most of the time is a pretty big\n" - "downside.\n" - "\n" - "\n" - "From what I have seen the only truly interesting case for extending\n" - "waitid is something file descriptor based so the parent/child\n" - "relationship is not necessary to wait for a process to terminate.\n" - "\n" - "As for getrusage. If a sane union of the rusage limits and cgroups or\n" - "something like cgroups could be devised. That would be ideal. Of\n" - "course except for the memory cgroups the similarity to the resource\n" - "usage measurments and limits really isn't there. So I don't know if\n" - "merging them would be a real possibility.\n" - "\n" - "So I suspect the simplest thing to do would be to set a flag in the\n" - "idtype member of waitid that says give me rusage64 and then we would\n" - "be done. Alternately we could use the low bits of the resource usage\n" - "pointer. Assuming we don't want to introduce another syscall that is.\n" - "I really don't see much incremental extensibility potential in the wait\n" - "or rusage interface right now.\n" - "\n" - Eric + downside. -94e59ef0c372a8ca121d8c9e28df123a97766d15c8545840e3d03dae7f3b6034 +f4a18a8ef16696a3b4be32fbbeb8a5387ee57cd83124eeaee54ac1ec21dade0e
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.