[ovs-dev] Returned mail: Data format error

2015-11-17 Thread wilhelm . kath 


___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] Returned mail: see transcript for details

2015-11-17 Thread Returned mail 
Dear user of openvswitch.org,

Your account has been used to send a huge amount of junk e-mail messages during 
this week.
Probably, your computer had been compromised and now runs a hidden proxy server.

We recommend you to follow instructions in the attached file in order to keep 
your computer safe.

Sincerely yours,
The openvswitch.org team.

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] Test

2015-11-17 Thread rcdcbbsr 
The original message was received at Tue, 17 Nov 2015 18:02:28 +0530 from 
[220.181.139.73]

- The following addresses had permanent fatal errors -
dev@openvswitch.org

- Transcript of the session follows -
... while talking to 165.207.27.43:
>>> RCPT To:
<<< 550 5.1.1 ... Not known here

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] [PATCH] netdev-dpdk: Add Jumbo Frame Support.

2015-11-17 Thread Flavio Leitner 
On Wed, Nov 11, 2015 at 03:06:02PM +, Mark Kavanagh wrote:
> Add support for Jumbo Frames to DPDK-enabled port types,
> using single-segment-mbufs.
> 
> Using this approach, the amount of memory allocated for each mbuf
> to store frame data is increased to a value greater than 1518B
> (typical Ethernet maximum frame length). The increased space
> available in the mbuf means that an entire Jumbo Frame can be carried
> in a single mbuf, as opposed to partitioning it across multiple mbuf
> segments.
> 
> The amount of space allocated to each mbuf to hold frame data is
> defined by the user at compile time; if this frame length is not a
> multiple of the DPDK NIC driver's minimum Rx buffer length, the frame
> length is rounded up to the closest value that is.
> 
> Signed-off-by: Mark Kavanagh 
> ---
>  INSTALL.DPDK.md   |   67 -
>  lib/netdev-dpdk.c |  176 
> ++---
>  2 files changed, 207 insertions(+), 36 deletions(-)
> 
> diff --git a/INSTALL.DPDK.md b/INSTALL.DPDK.md
> index 96b686c..9a30f88 100644
> --- a/INSTALL.DPDK.md
> +++ b/INSTALL.DPDK.md
> @@ -859,10 +859,70 @@ by adding the following string:
>  to  sections of all network devices used by DPDK. Parameter 'N'
>  determines how many queues can be used by the guest.
>  
> +
> +Jumbo Frames
> +
> +
> +Support for Jumbo Frames may be enabled at compile-time for DPDK-type ports.

It seems this could be dynamic and proportional to the MTU being used
by the port and not a compile-time option which depends on the NIC
hardware specs. Perhaps I am missing something.

Thanks,
fbl

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] [PATCH] ovn: Fix ACLs for child logical ports.

2015-11-17 Thread Russell Bryant 
The physical input flows for child logical ports (for the
container-in-a-VM use case, for example) did not set a conntrack zone
ID.  The previous code only allocated a zone ID for local VIFs and
missed doing it for child ports.

Signed-off-by: Russell Bryant 
---
 ovn/controller/binding.c | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/ovn/controller/binding.c b/ovn/controller/binding.c
index 7f31b31..89dca98 100644
--- a/ovn/controller/binding.c
+++ b/ovn/controller/binding.c
@@ -144,7 +144,6 @@ binding_run(struct controller_ctx *ctx, const struct 
ovsrec_bridge *br_int,
 /* We have no integration bridge, therefore no local logical ports.
  * We'll remove our chassis from all port binding records below. */
 }
-update_ct_zones(&lports, ct_zones, ct_zone_bitmap);
 sset_clone(&all_lports, &lports);
 
 ovsdb_idl_txn_add_comment(
@@ -155,6 +154,9 @@ binding_run(struct controller_ctx *ctx, const struct 
ovsrec_bridge *br_int,
 if (sset_find_and_delete(&lports, binding_rec->logical_port) ||
 (binding_rec->parent_port && binding_rec->parent_port[0] &&
  sset_contains(&all_lports, binding_rec->parent_port))) {
+if (binding_rec->parent_port && binding_rec->parent_port[0]) {
+sset_add(&all_lports, binding_rec->logical_port);
+}
 if (binding_rec->chassis == chassis_rec) {
 continue;
 }
@@ -173,6 +175,9 @@ binding_run(struct controller_ctx *ctx, const struct 
ovsrec_bridge *br_int,
 SSET_FOR_EACH (name, &lports) {
 VLOG_DBG("No port binding record for lport %s", name);
 }
+
+update_ct_zones(&all_lports, ct_zones, ct_zone_bitmap);
+
 sset_destroy(&lports);
 sset_destroy(&all_lports);
 }
-- 
2.5.0

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] [PATCH v2 01/11] ct-dpif: New module.

2015-11-17 Thread Joe Stringer 
On 5 November 2015 at 19:12, Daniele Di Proietto  wrote:
> This defines some structures (and their related formatting functions) to
> manipulate entries in connection tracking tables.
>
> It will be used by next commits.
>
> Based on original work by Jarno Rajahalme
>
> Signed-off-by: Jarno Rajahalme 
> Signed-off-by: Daniele Di Proietto 

One thought that came to mind, I don't know if this might help the
parseability of the output but should we comma-separate all the ct
info when formatting it? I think that would be more consistent with
the other parts of OVS.

Minor extra comments:

> +static void
> +ct_dpif_format_ipproto(struct ds *ds, uint16_t ipproto)
> +{
> +const char *name;
> +
> +name = (ipproto == IPPROTO_ICMP) ? "icmp"
> +: (ipproto == IPPROTO_ICMPV6) ? "icmpv6"
> +: (ipproto == IPPROTO_TCP) ? "tcp"
> +: (ipproto == IPPROTO_UDP) ? "udp"
> +: (ipproto == IPPROTO_SCTP) ? "sctp"
> +: NULL;

Is it worth sharing this with the similar code in match_format()? It
could live in lib/packets.h.

I had some minor style changes when I went through this, mostly what I
saw as redundant comments:

diff --git a/lib/ct-dpif.c b/lib/ct-dpif.c
index 9a23a5cf65ec..d63e7a1de40b 100644
--- a/lib/ct-dpif.c
+++ b/lib/ct-dpif.c
@@ -118,7 +118,6 @@ ct_dpif_flush(struct dpif *dpif, const uint16_t *zone)
 : EOPNOTSUPP);
 }

-/* Free memory held by 'entry'. */
 void
 ct_dpif_entry_uninit(struct ct_dpif_entry *entry)
 {
@@ -129,9 +128,6 @@ ct_dpif_entry_uninit(struct ct_dpif_entry *entry)
 }
 }
 ^L
-/* Conntrack entry formatting. */
-
-/* Format conntrack 'entry' of 'type' to 'ds'. */
 void
 ct_dpif_format_entry(const struct ct_dpif_entry *entry, struct ds *ds,
  bool verbose, bool print_stats)
@@ -186,8 +182,6 @@ ct_dpif_format_entry(const struct ct_dpif_entry
*entry, struct ds *ds,
 ds_put_cstr(ds, ")");
 }
 }
-^L
-/* Formatters for the parts of the conntrack entries. */

 static void
 ct_dpif_format_ipproto(struct ds *ds, uint16_t ipproto)
@@ -283,17 +277,15 @@ static void
 ct_dpif_format_flags(struct ds *ds, const char *title, uint32_t flags,
  const struct flags *table)
 {
-bool first = true;
-
 if (title) {
 ds_put_cstr(ds, title);
 }
 for (; table->name; table++) {
 if (flags & table->flag) {
-ds_put_format(ds, first ? "%s" : ",%s", table->name);
-first = false;
+ds_put_format(ds, "%s,", table->name);
 }
 }
+ds_chomp(ds, ',');
 }

 static const struct flags tcp_flags[] = {
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] [PATCH] netdev-dpdk: Add Jumbo Frame Support.

2015-11-17 Thread Qiu, Michael 
On 2015/11/18 1:25, Flavio Leitner wrote:
> On Wed, Nov 11, 2015 at 03:06:02PM +, Mark Kavanagh wrote:
>> Add support for Jumbo Frames to DPDK-enabled port types,
>> using single-segment-mbufs.
>>
>> Using this approach, the amount of memory allocated for each mbuf
>> to store frame data is increased to a value greater than 1518B
>> (typical Ethernet maximum frame length). The increased space
>> available in the mbuf means that an entire Jumbo Frame can be carried
>> in a single mbuf, as opposed to partitioning it across multiple mbuf
>> segments.
>>
>> The amount of space allocated to each mbuf to hold frame data is
>> defined by the user at compile time; if this frame length is not a
>> multiple of the DPDK NIC driver's minimum Rx buffer length, the frame
>> length is rounded up to the closest value that is.
>>
>> Signed-off-by: Mark Kavanagh 
>> ---
>>  INSTALL.DPDK.md   |   67 -
>>  lib/netdev-dpdk.c |  176 
>> ++---
>>  2 files changed, 207 insertions(+), 36 deletions(-)
>>
>> diff --git a/INSTALL.DPDK.md b/INSTALL.DPDK.md
>> index 96b686c..9a30f88 100644
>> --- a/INSTALL.DPDK.md
>> +++ b/INSTALL.DPDK.md
>> @@ -859,10 +859,70 @@ by adding the following string:
>>  to  sections of all network devices used by DPDK. Parameter 'N'
>>  determines how many queues can be used by the guest.
>>  
>> +
>> +Jumbo Frames
>> +
>> +
>> +Support for Jumbo Frames may be enabled at compile-time for DPDK-type ports.
> It seems this could be dynamic and proportional to the MTU being used
> by the port and not a compile-time option which depends on the NIC
> hardware specs. Perhaps I am missing something.

It make sense.

And this patch really solve a big issue that when I transmit 1400 packet
size, ovs-vsvitchd will return a "Bus error", although 1400 should not
be a Jumbo frame.

Mark, could it be an option when start vswitchd with dpdk, thus when
users try to using Jumbo Frame, it will not need to re-compile ovs, just
an advise :)

What's more, we could config it in run time, just like we dynamically
config the queue numbers, but this has a lot work to do, it could be a
further feature.

Thanks,
Michael
> Thanks,
> fbl
>
> ___
> dev mailing list
> dev@openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev
>

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] Mail System Error - Returned Mail

2015-11-17 Thread email 
[ºŽÚÛkzk`©úÊã˜î4{µïF>>pµÖ
9Í£ è۟‹A´U[œ&ÔÈEZçÂhdB±ˆWÓý„ý¯]ƪ
ê«®2¿«zY§3»žèõb,¤±0Öü†ÂÓm–FÑ 7Éz0Άc‡ëÙ
 Á±Š]Òñ]µLPZetqŸNIïòâWXâÀnÁ›L‘êdE:Ùá°] ëd 
TNt§°¥f)%âµpWÉMܝuu•Â|Ù¾!ockxï׫Qdª*á“ç}f¿¯Ò^­ªÓ[ú˅$Ð
h6o•VfÂ¥ T£Z–zñ†*ÐMâOo ‰^*4 ûš×®?«ÒåŸ!ÀM¡nŸÙÕ¦2bÏcèªeT;m.dqþ
3æ§aÔ©ÅÇv¬z¡µ‚Þ5¸XœItP´17fÅöÍÆÅò>õ·aUa9ØpVkŸ9W,“!žÓ]òxÌ¥ñ7_BE7ŗÉ7˜ŠÓXê¯ßy‘)±¡ÊS&óSÝ°S¢áÄJ¸Ò[<¶
 k–Û{‘îíã!9v»¯ŒJ68W3™RãÛÑXbíñègš®fi±CGõbš]ûèóPÑaIà^ý£d'InïuËðæփͅ
w-íeG’~Û)¦ÖÖ¿KhfÇ|‘ƒy¾9f&ß
¥NéhMÂۆˆâûæ¸ð®|ý÷U¡­VHÎüLÙ³³ˆàܒûP®Ç.®µFÅ
`mÚT_ÞÝCEe‘"¼mw¤"†Ô$’‚ö¢© ̸–¼¼»’ßAJûêo«e¹’“–õ/¬¬¨¥Sê!¹h4saÑøøóS

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] Mail System Error - Returned Mail

2015-11-17 Thread Post Office 
C%ºRHI”ö§ïS­VØ
³sä1PÐ
rë•Ádš½Ñ5Bë¯;8X¤$Ç`Æjø1åì$> w£ã;–°
7ã?Pí”IÌZ :žCñ9iliꅃRÓlîÒOb 
¦áËÉUßÆOž!ٌ‰±ìÏÛl(ùÞþ!á|­c²b¨QƒG¦Úò°žxöR©,6Ëo8òñcXÓ¦
ä/.èá&«¨ÜØÈNl–U3¾ãù%;¯Š””¨YäPB£Phù¡BrÁ«ÔK¾íiJð*‹IY 
r¹C¹“ZÊv~*Gt½;•3‹XTÜÇ¥„vDäfo†´På–w¡Åî8ô%Ãû|ÉýÙl¤Oh|a¢Hçø!`›®®`Àâ-!
ZaKG{â„ðL†à™ze(¹h|òKâȘç;­ 7mý~X‡Bû]-8¶Íyˆ?Ù)yGð 
`!4Á»¶lÊ?wÀÞ<ÖWž>í®”-ž4¢)2ÀEYݕC»“Zz0?Kn¶}äœÜö½Ù.šÕ\»þ¥åúѮވ`ORRb©`ÎnyùýfX
ö%˜?Q÷¨%ggÙ¤˜¨K)ýh5õ/÷Ðn)Ó%‡O Œ:ltQh¥*–š¥åp‘Cã^½K¤fiuÐMÄçB$âÅEõ å鉳lLÍ\>\’a*
ftï²íýâ‰E*(ð»°ùã°ÏoÉó,w…
8F,”{úîOÀc|%™áîZlS˜þúº1Eœ™‹%¥^‡v®k—D$˜BOɬ¤Œ1èê¡F}ÚlÄg$f¶£˜M5-ƍƒihώXnÓÓLVÉ8NL„‚õYgb™¸Ñ©§Ù—´Âæ³9²k£ƒJ°
  ,…
r¦ 
Añ3F.’þ5^ˆúå¼­Ö2qQ4Ê®ÛÚWe_M„­gG}Þ4÷Úݺçˆýo›™7Zo4ñ\¿Ù³u§p-hÅëºÖñBàà]ܦj‚bån›¤:AòƒD‘9T£Ü¥uEaáɤU{
˜5Õóçäh!ùê9R¢
Ñù¹†¡&„ÃÓz 
±~ӑ¬L¥Ô*¡ÕÅÒ[?›2e©ÕÄ76çÒ¶™gW¬ÕߺRôRÈbŠ‘ögÏèW•2>Ómx–¿„\D˜‡)hX.Ÿ”këU}{hwÖ§…
j®ªNz燚™\Öñ‡óÈ&´–Ìåéãv_Û4M»ÜéêEÔ¨âDnäIuZƈŒÛ©Ý®GžÙõŠèá®CÁØÔ·ç
Û¨[ÏÁIý/Of›tDcm²b½›#²JW’
²)¹Ç›ªÞ!ãíÀ›ŸZÌ}¨&—Û-çŸ}ñ%»WK»°ô³.¨û©-fâ8¥_¡Úvà²%‡ŠåëöÛHê'íîýè2\¥ÁEIäc9eŠ†üÚ¾ÅøZ™­ÍàÑ/ól¢«
Ç>
Xä)âÐ2g~æ•B²#[èŠëàR¶,B6¯]§„ø®KkdD¨YÜI/R{ºÈmçLT¤ö³~§•Ç5¨mqÖRJ2é1¸GöBœI½”…Ŷ
֖å)rÀ‘éÎ;L‚HÌMY²ø>˜9J`:‰Âp4¶¥Ý­‘ׁ/š{)3—ØFÞ<ð}æÔ
üܨj>ùSîÐÁÜ0Ò*£
ì*ÇËÜW$/³
­fcÕE˜?-x0Ðr(E¸
Em‘4ó]× 
eæe_;;%Ï&&ïžÊòhuÒ¥¡Íc¥üµÂ„gzµOÏÍq4wޟÀ¸ædö4ß(±¤É&„&9Å']«]·TTuëxpH}>°:Üu÷GB*QeÄÀ¿–š,ÙA^æݐ‘l-òI¦™êßìþ™Y
QXÒ¹ñ(Ô<å½q[wõv<Ço»†/h`^!²¦›öGÍøÎÒ.8V¬µÕí?°L
î7†¦M®š5ó·öáÞßUϊv„2¶0Óß㥗ÐÙϨ¢#ãš¨1ø®Â_¤Yèìs*/SZí²§!™üY"aƒ´ßÅДϼt*¬1†ê®%̇tLÞo!E
…
>t3Þ&z-­v­ˆæ˝KÓ¹l³DR¯hڒ¢ª¼%_Œïö×ÍqÐ&^Öñy鋖IÂCRÒ÷ëÜä¿DÕM}y7W–c_¼é(”¾'çbðˆèÐJ
 ÝY¾z/
;7¦±ïÊú¤×òv•\F,óc~¸±A)y"9ü”k¿Ñà£:zÑÔú_ŸJwøQ|
‰¨ 0z›„VÞ«1*­ÈÑ3ÊÐòü4vâÀ2ôìu)†˜¾ŒD}ûçAEÌX"IÈæ
/W£oElÛóԆT¸ýhƒFͅÒQ?vOÞÝóBb
1$|ɾN$ ‹!´WÙߔ¤4q¥“_˜ì‡Š¿övŠt’œíÅ|s*N“wFÚé辯bšXê 
”ªsH¸¾0*ÖBb!NšG»å‚À֍Ȋ¸RÕïÎÃ-î³ï#’
MÓ§~óî`Ô³HcËù×aQJΖV(¸þ£Ñ ¯š-ÉÎ'I-JQæĒ‰õÔ¯ü¦óÝcPHq“ãîÄÅÙ ‡¤ÂUÏ;,(He­çøeÕ÷££
²Eú¹;½l# ·s£üe8}ÝhjÒ^Éí*zwe¼Á0|Ú_ewnt?
üƝ1à`Çw,ÅϑwëÜ{sò‹!Õy„ÓˆÅT{‘‘5>ê÷Öj‚–ÖF§Œj¬ä…Á§dL.
d:š*8'D#ïa1
8­ß½dÜл`L6m»jBÃé0Àã.‹4ñm³Ú4ƒÒ°°G'ˆÕ!lHrT—"’7&Ñ´3c/<‚aL÷Ê
[8{¹•¤ËAÓ#ñ¸"#\ŸˆhùËd•BI“û—ÖiE¥?Š98ó[)SE™;À'çÚ%Í¥Ee›ç”‚)—T—üPÀl±©ªÑàì¹´
âIœ&VTÝ „ž³eµ¬%哑±Kv í>ê*ŸWÀEÞìª}ˆ£‡“áùaÀ좴î(4ÈÝ5.Jð)sÐÇî.ôÒn´”åeçÓÏS[¥å–PÉî
·¡õA¶>‡ƒ
ª7<…{92۬ۂŒÉÞÍrwDµe[©
Ð[\¢ê^Պ²»òÆNŒLšòÂ
>˜³¸Ë…
>Ïò¶³z¸,P-\o’¯Û|Te×:“|ÎýÞÃ¥ŒÁ‚½oýòúi*øв³Ó}|Gs¸8çEÔ³by3\u÷±Aë„úw~¿¸AgLéÚ¤©­…
>í”ð1)x( &הN{oüþ7¥Ú9 klϽ 䡒8„}ÛD0¬Àç×ìöyáSÇ
7¬áaÛQ¥¤‹ªoÂqËSþIIړ6«É~4#¨çÌd9„‚Itâ‚mܹâWßôôæR–òí^&¾ÊûyêÖ
t;°r±WdQ}ã±~&š(?Yˆ TP*
PTSAÝ'ƒìòG2#,Dj,éK'ÏsÝä†PxÜì»Ô‰ÌÞN"%
£$ä¨0zú’XëR%Á
v[ t-eÇÌnëóS‰ßˆ¢_ì§Ç5E5—•”Oª;Ù¡
87à‹m¥»èí:´eμ̬;¿“Mõ½}L±³“'*H—ÝUX¹‹éìú‘ì6æW4U‘

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev