ipmr: delete redundant variable
Subsystems (3)
PATCH 1/2 ipmr: delete redundant variable
*v can be removed as this patch showing.
---
net/ipv4/ipmr.c +3 -4
@@ -1121,7 +1121,6 @@ int ipmr_ioctl(struct sock *sk, int cmd, void __user *arg)static int ipmr_device_event (struct notifier_block *this,unsigned long event,void *ptr) {struct net_device *dev = ptr; -struct vif_device *v;int ct;if (!net_eq (dev_net (dev), &init_net))
@@ -1129,9 +1128,9 @@ static int ipmr_device_event(struct notifier_block *this, unsigned long event, vif (event !=NETDEV_UNREGISTER )return NOTIFY_DONE ; - v=&vif_table[0 ]; -for (ct=0 ;ct<maxvif;ct++,v++) { -if (v->dev==dev) + +for (ct =0 ; ct < maxvif; ct++) { +if (vif_table[ct].dev == dev)vif_delete (ct,1 ); }return NOTIFY_DONE ;
Hi Wang Chen,
Quoted 1 line · Wang Chen
*v can be removed as this patch showing.
You are right, but did you check the resulting asm?
net/ipv4/ipmr.c static int ipmr_device_event(struct notifier_block *this, unsigned long event, v · line 1134
Quoted 13 lines
Signed-off-by Wang Chen <[email protected]>---
net/ipv4/ipmr.c +0
-3@@ -1129,9 +1128,9 @@ static int ipmr_device_event(struct notifier_block *this, unsigned long event, vif (event !=NETDEV_UNREGISTER )return NOTIFY_DONE ; - v=&vif_table[0 ]; -for (ct=0 ;ct<maxvif;ct++,v++) { -if (v->dev==dev)
This is ptr += sizeof(vif_table[0])
net/ipv4/ipmr.c static int ipmr_device_event(struct notifier_block *this, unsigned long event, v · line 1133
Quoted 3 lines
net/ipv4/ipmr.c +3
-0+ +for (ct =0 ; ct < maxvif; ct++) { +if (vif_table[ct].dev == dev)
This is ptr + ct * sizeof(vif_table[0])
On architectures, where the second address variant is not supported, it spills a register with the multiply/shift.
But the second variant could be easily auto vectorized, if we had no if.
So just check the asm on a CISC and a RISC architecture with a cross compile, before you transform these patterns.
Maybe GCC even transform one into the other these days :-)
Best Regards
Ingo Oeser
Ingo Oeser said the following on 2008-7-23 16:03:
Quoted 23 lines
Hi Wang Chen,
Quoted 1 line · Wang Chen
*v can be removed as this patch showing.
You are right, but did you check the resulting asm?
net/ipv4/ipmr.c static int ipmr_device_event(struct notifier_block *this, unsigned long event, v · line 1134
Quoted 13 lines
Signed-off-by Wang Chen <[email protected]>---
net/ipv4/ipmr.c +0
-3@@ -1129,9 +1128,9 @@ static int ipmr_device_event(struct notifier_block *this, unsigned long event, vif (event !=NETDEV_UNREGISTER )return NOTIFY_DONE ; - v=&vif_table[0 ]; -for (ct=0 ;ct<maxvif;ct++,v++) { -if (v->dev==dev)This is ptr +=
sizeof(vif_table[0])
Quoted 9 lines
net/ipv4/ipmr.c static int ipmr_device_event(struct notifier_block *this, unsigned long event, v · line 1133
Quoted 3 lines
net/ipv4/ipmr.c +3
-0+ +for (ct =0 ; ct < maxvif; ct++) { +if (vif_table[ct].dev == dev)This is ptr + ct *
sizeof(vif_table[0])On architectures, where the second address variant is not supported, it spills a register with the multiply/shift.
But "accessing entry of table by index" is always allowed, right?
If the complier makes such pointer which spills a register with the multiply/shift, the simple code as following is bug too:
i = table[100].field;
But it shouldn't, right :)
Quoted 7 lines
But the second variant could be easily auto vectorized, if we had no if.
So just check the asm on a CISC and a RISC architecture with a cross compile, before you transform these patterns.
Maybe GCC even transform one into the other these days :-)
Hi Wand Chen,
Quoted 6 lines · Wang Chen
But "accessing entry of table by index" is always allowed, right?
If the complier makes such pointer which spills a register with the multiply/shift, the simple code as following is bug too:
i = table[100].field;
But it shouldn't, right :)
I'm NOT telling you, that your transformation is introducing a BUG. It is semantically perfectly equivalent.
I'm trying to tell you, that it might not led to the same or better performance and might thus be not worth it.
But please check the generated assembly yourself on a CISC and RISC machine to get an idea of the effects. It will be a nice learning experience I enjoyed myself already.
Best Regards
Ingo Oeser
Ingo Oeser said the following on 2008-7-23 20:05:
Quoted 10 lines
Hi Wand Chen,
Quoted 6 lines · Wang Chen
But "accessing entry of table by index" is always allowed, right?
If the complier makes such pointer which spills a register with the multiply/shift, the simple code as following is bug too:
i = table[100].field;
But it shouldn't, right :)
Quoted 6 lines
I'm NOT telling you, that your transformation is introducing a BUG. It is semantically perfectly equivalent.
I'm trying to tell you, that it might not led to the same or better performance and might thus be not worth it.
Agree. I also think the accessing by index might lead to worse performance. But in this code, we don't care performance, since it only be called when device is unregistered. :)
Quoted 4 lines
But please check the generated assembly yourself on a CISC and RISC machine to get an idea of the effects. It will be a nice learning experience I enjoyed myself already.
Sure. I am doing it.
Ingo Oeser said the following on 2008-7-23 20:05:
Quoted 4 lines
But please check the generated assembly yourself on a CISC and RISC machine to get an idea of the effects. It will be a nice learning experience I enjoyed myself already.
I did the experiment.
I used the following C code to compare which approach is better and get a result that two are same on performance.
----main.c
#define maxvif 32
struct vif {
int *dev;
unsigned long bytes_in, bytyes_out;
unsigned long pkt_in, pkt_out;
unsigned long rate_limit;
unsigned char threshhold;
unsigned short flags;
int local, remote;
int link;
};struct vif vif_table[maxvif];
int main()
{
struct vif *v;
int ct;
v = &vif_table[0];
for (ct = 0; ct < maxvif; ct++, v++)
if(v->link==1)
break;
return 0;
}---
---main2.c
#define maxvif 32
struct vif {
int *dev;
unsigned long bytes_in, bytyes_out;
unsigned long pkt_in, pkt_out;
unsigned long rate_limit;
unsigned char threshhold;
unsigned short flags;
int local, remote;
int link;
};struct vif vif_table[maxvif];
int main()
{
struct vif *v;
int ct;
v = &vif_table[0];
for (ct = 0; ct < maxvif; ct++)
if(vif_table[ct].link==1)
break;
return 0;
}---
Use gcc -S -O2 to compile:
---x86 asm main.s
.file "main.c" .text .p2align 4,,15 .globl main .type main, @function main: leal 4(%esp), %ecx andl $-16, %esp pushl -4(%ecx) movl $vif_table, %eax pushl %ebp movl %esp, %ebp pushl %ecx jmp .L2 .p2align 4,,7 .L8: cmpl $vif_table+1240, %eax je .L3 addl $40, %eax .L2: cmpl $1, 36(%eax) jne .L8 .L3: popl %ecx xorl %eax, %eax popl %ebp leal -4(%ecx), %esp ret .size main, .-main .comm vif_table,1280,32 .ident "GCC: (GNU) 4.1.2 20070115 (prerelease) (SUSE Linux)" .section .note.GNU-stack,"",@progbits
---
---x86 asm main2.s
.file "main2.c" .text .p2align 4,,15 .globl main .type main, @function main: leal 4(%esp), %ecx andl $-16, %esp pushl -4(%ecx) xorl %eax, %eax pushl %ebp movl %esp, %ebp pushl %ecx jmp .L2 .p2align 4,,7 .L8: addl $40, %eax cmpl $1280, %eax je .L3 .L2: cmpl $1, vif_table+36(%eax) jne .L8 .L3: popl %ecx xorl %eax, %eax popl %ebp leal -4(%ecx), %esp ret .size main, .-main .comm vif_table,1280,32 .ident "GCC: (GNU) 4.1.2 20070115 (prerelease) (SUSE Linux)" .section .note.GNU-stack,"",@progbits
---
In loop area, main.s and main2.s have the following difference:
main.s :
cmpl $vif_table+1240, %eax cmpl $1, 36(%eax) main2.s: cmpl $1280, %eax cmpl $1, vif_table+36(%eax)
The difference can't cause different performance.
OK. Here is the asm on SPARC(not cross compile)
---main.s
.global main
main:
/* 000000 21 */ sethi %hi(vif_table),%o5 /* 0x0004 22 */ or %g0,0,%o4 /* 0x0008 21 */ add %o5,%lo(vif_table),%o3 /* 0x000c 23 */ ld [%o3+36],%o5
.L900000106:
/* 0x0010 23 */ cmp %o5,1
/* 0x0014 */ be,pn %icc,.L77000028
/* 0x0018 22 */ add %o4,1,%o4
.L77000025:
/* 0x001c 22 */ add %o3,40,%o3
/* 0x0020 */ cmp %o4,32
/* 0x0024 */ bl,a,pt %icc,.L900000106
/* 0x0028 23 */ ld [%o3+36],%o5
.L77000028: /* 0x002c 22 */ retl ! Result = %o0 /* 0x0030 */ or %g0,0,%o0 /* 0x0034 0 */ .type main,2 /* 0x0034 0 */ .size main,(.-main) /* 0x0034 0 */ .global __fsr_init_value
/* 0x0034 */ __fsr_init_value=0
---
---main2.s
.global main
main:
/* 000000 22 */ sethi %hi(vif_table+36),%o5
/* 0x0004 */ or %g0,0,%o3
/* 0x0008 */ add %o5,%lo(vif_table+36),%o4
/* 0x000c 23 */ ld [%o5+%lo(vif_table+36)],%o5
.L900000106:
/* 0x0010 23 */ cmp %o5,1
/* 0x0014 */ be,pn %icc,.L77000028
/* 0x0018 22 */ add %o4,40,%o4
.L77000025:
/* 0x001c 22 */ add %o3,1,%o3
/* 0x0020 */ cmp %o3,32
/* 0x0024 */ bl,a,pt %icc,.L900000106
/* 0x0028 23 */ ld [%o4],%o5
.L77000028: /* 0x002c 22 */ retl ! Result = %o0 /* 0x0030 */ or %g0,0,%o0 /* 0x0034 0 */ .type main,2 /* 0x0034 0 */ .size main,(.-main) /* 0x0034 0 */ .global __fsr_init_value
/* 0x0034 */ __fsr_init_value=0
---
In loop area, they are both ptr+sizeof(struct).
Now, we can get a conclusion that current compiler can do optimize the index accessing. :)
Ingo, if you have any different opinion, it will be appreciated that you can share. :)
Hi Wang Chen,
Quoted 7 lines · Wang Chen
Ingo Oeser said the following on 2008-7-23 20:05:
Quoted 4 lines
But please check the generated assembly yourself on a CISC and RISC machine to get an idea of the effects. It will be a nice learning experience I enjoyed myself already.
I did the experiment.
[..]
Quoted 6 lines
In loop area, they are both ptr+sizeof(struct).
Now, we can get a conclusion that current compiler can do optimize the index accessing. :)
Ingo, if you have any different opinion, it will be appreciated that you can share. :)
Great! Compilers improved a lot here :-)
Many thanks for doing this experiment.
Now you and others can anyone who is is questioning
this fact to your experiment and take it as a reference for similiar changes.
That is a great help for the community, I think!
Best Regards
Ingo Oeser