Dnia Monday 26 of May 2008, napisałeś: > Dnia Monday 26 of May 2008, Gerrit Renker napisał: > > | As for information we can get from kernel wrt dccp we have at least: > > | 1. fixed information that depends only on kernel version. For example > > | list of ccids, list of available qpolicies, list of parameters for > > | given qpolicy, etc. These are system wide and don't need reference to > > | socket. These could even be exposed by read-only entries in /sys or > > | /proc. > > > > That is a good point - I think Arnaldo had a similar idea once for > > implenting system-wide policies regarding which CCIDs are supported. > > Something like net.ipv4.tcp_available_congestion_control. > > Ok, we may go this way. I'll try to write a patch in a few days (quite busy > now). > Now that I had a closer look at implementing this functionality I have a few questions: 1. Where should information about available qpolicies and their parametrs be exported? Would /proc/net/dccp/qpolicies/ be a good choice? 2. I guess we should have at least one file per qpolicy with parameters listed inside. Like that: /proc/.../qpolicies/simple: <empty> /proc/.../qpolicies/prio: 1 (DCCP_SCM_PRIORITY) 2 (DCCP_SCM_TIMEOUT) But we could also have qpolicy represented by directory and parameters by files: /proc/.../qpolicies/simple/ /proc/.../qpolicies/prio/ /proc/.../qpolicies/prio/priority: <empty> /proc/.../qpolicies/prio/timeout: <empty> Which layout do you find better? -- Regards, Tomasz Grobelny -- To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
