Re: kernel guide to space (updated)
Jan Engelhardt wrote:
>>3e. sizeof
>> space after the operator
>> no space if the operand is in barces
>>
>>
>
>braces
>
>
>
>>3f. Braces etc
>> () [] -> .
>>
>>
>
>() parentheses (short form: parens)
>[] square brackets
>{} braces
><> dunno their name :p
>
angle brackets, it's all nicely explained at
http://en.wikipedia.org/wiki/Bracket
--
Joost
smime.p7s
Description: S/MIME Cryptographic Signature
Re: strange incremental patch size [2.6.12-rc2 to 2.6.12-rc3]
Maciej Soltysiak wrote: >Hi, > >These are the sizes of rc2 and rc3 patches > ># ls -la patch-2.6.12* >-rw-r--r-- 1 root src 18011382 Apr 4 18:50 patch-2.6.12-rc2 >-rw-r--r-- 1 root src 19979854 Apr 21 02:29 patch-2.6.12-rc3 > >Let us make an incremental patch from rc2 to rc3 > ># interdiff patch-2.6.12-rc2 patch-2.6.12-rc3 >x > >Let us see how big it is. ># ls -ld x >-rw-r--r-- 1 root src 37421924 Apr 21 12:28 x > >How come interdiff from rc2 (18MB) to rc3 (20MB) gave me >37MB worth of patch-code ? I would expect something about >2MB but 40MB ? > > > The order in the patch changed a lot. The rc2 patch starts with the changes in the CREDITS file and the rc3 patch has those starting at line 151839. This is probably because Linus now uses different tools to produce these. Maybe you can somehow sort the rc2 patch in the same way as the rc3 patch (same file order) before using interdiff, that should solve it. Joost >The patching with the incremental patch took very long compared >to other rc2-rc3-type patches, that is how I noticed it. > >Regards, >Maciej > > >- >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >the body of a message to [EMAIL PROTECTED] >More majordomo info at http://vger.kernel.org/majordomo-info.html >Please read the FAQ at http://www.tux.org/lkml/ > > smime.p7s Description: S/MIME Cryptographic Signature
Re: [patch 1/1] /proc/$$/ipaddr and per-task networking bits
On Thu, 2005-03-10 at 17:08 +0100, Arjan van de Ven wrote: > On Thu, 2005-03-10 at 17:00 +0100, Lorenzo HernÃndez GarcÃa-Hierro > wrote: 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. > > but... a use doesn't hane an IP. a host does. I'm not sure i understand but i've just tried to read the code and it looks like the IP address is the address of the other end of a socket. This address is set when a process does accept(). So this user IP we are talking about would be the remote users host IP (or gateway in case of NAT). I don't think i fully understand the code but it looks like it only holds the remote IP address of the last accept()-ed connection. Joost Remijn signature.asc Description: This is a digitally signed message part
