[lkml]   [2005]   [Mar]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch 1/1] /proc/$$/ipaddr and per-task networking bits
El jue, 10-03-2005 a las 16:38 +0100, Arjan van de Ven escribió:
> but.... tasks don't have an IP address. Hosts do. Hosts can have
> multiple IP addresses. Both ipv4 and ipv6. Users don't have IP
> addresses either (they do have user IDs so that link is clear).
> I think I'm missing something big here. What does it *mean* for a task
> to have an IP address. Once that is clear maybe I can start to
> understand the rest, but until the meaning of "task has an IP address"
> is better explained/more clear I think I'm stuck. (and no the output in
> a log isn't a meaning, it's only a result)

I think I've explained it well, more concretely, it tries to fill the
ipaddr member of the task_struct structure with the IP address
associated to the user running @current task/process,if available.
Then, it will be attached within the proc fs in an entry called ipaddr,
under the proper pid directory.

The whole thing is almost self-explaining by just looking at the code.

Lorenzo Hernández García-Hierro <>
[1024D/6F2B2DEC] & [2048g/9AE91A22][]
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2005-03-22 14:11    [W:0.065 / U:1.232 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site