Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\]\s+ipvs\:\s+provide\s+iph\s+to\s+schedulers\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\]\s+ipvs\:\s+provide\s+iph\s+to\s+schedulers\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [PATCH net-next] ipvs: provide iph to schedulers (score: 1): Author: Simon Horman <horms@xxxxxxxxxxxx>; Date: Wed, 19 Jun 2013 09:29:42 +0900; Thanks, I have queued this up for v3.11 in ipvs-next. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info; /html/lvs-devel/2013-06/msg00049.html (27,208 bytes)
2. Re: [PATCH net-next] ipvs: provide iph to schedulers (score: 1): Author: Hans Schillstrom <hans@xxxxxxxxxxxxxxx>; Date: Sun, 16 Jun 2013 11:23:30 +0200; Looks good to me. Acked-by: Hans Schillstrom <hans@xxxxxxxxxxxxxxx> Attachment: smime.p7s Description: S/MIME cryptographic signature; /html/lvs-devel/2013-06/msg00033.html (26,708 bytes)
3. [PATCH net-next] ipvs: provide iph to schedulers (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Sun, 16 Jun 2013 09:09:36 +0300; Before now the schedulers needed access only to IP addresses and it was easy to get them from skb by using ip_vs_fill_iph_addr_only. New changes for the SH scheduler will need the protocol and ports; /html/lvs-devel/2013-06/msg00030.html (22,595 bytes)

Current List: 1 - 3
Page: [1]