| To: | Nathan Scott <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [RFC] A privileged pmcd co-process |
| From: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
| Date: | Tue, 24 Jun 2014 07:57:37 -0400 |
| Cc: | PCP <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <1690334551.32241023.1403584004294.JavaMail.zimbra@xxxxxxxxxx> |
| References: | <1828964541.31278424.1403503516163.JavaMail.zimbra@xxxxxxxxxx> <25800551.31292134.1403505090072.JavaMail.zimbra@xxxxxxxxxx> <y0m38ev7db9.fsf@xxxxxxxx> <1690334551.32241023.1403584004294.JavaMail.zimbra@xxxxxxxxxx> |
| User-agent: | Mutt/1.4.2.2i |
Hi - > [...] In this cunning plan, there is only one pmcd, as now, and it > has only one helper co-process which provides services (in > particular, it serves namespace file descriptors) to the other pmcd > (IOW to DSO PMDAs) and to process PMDAs that export data that is > affected by specific namespaces. You're right, I did totally misread your suggestion. Let me try a second simplified rephrasing: you're envisioning the systemwide pmcd and pmda processes switching to/from container namespaces to service individual requests? Kind of like the linux_proc pmda doing temporary setuid() downgrades? - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates: getopt folio support, Nathan Scott |
|---|---|
| Next by Date: | nvidia/nvml pmda, Martins Innus |
| Previous by Thread: | Re: [RFC] A privileged pmcd co-process, Nathan Scott |
| Next by Thread: | Re: [RFC] A privileged pmcd co-process, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |