Re: [vpp-dev] UDP packet sending using sendto()
Hi Nataraj, It’s not possible with VCL at this point but it’s possible with builtin applications. It’s just a matter of extending the connect api to support this. Florin > On Sep 25, 2019, at 6:16 PM, Nataraj Batchu wrote: > > Hi, > > Today with VPP we cannot give endpoint info in sendto() call. We have to do a > connect(udp_sock, endpoint_info) first and then invoke sendto(). This works. > But the question is how can I influence the source port of these packets? > > Thanks, > -Nataraj -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#14057): https://lists.fd.io/g/vpp-dev/message/14057 > Mute This Topic: https://lists.fd.io/mt/34294099/675152 > Group Owner: vpp-dev+ow...@lists.fd.io > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [fcoras.li...@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14058): https://lists.fd.io/g/vpp-dev/message/14058 Mute This Topic: https://lists.fd.io/mt/34294099/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] UDP packet sending using sendto()
Hi, Today with VPP we cannot give endpoint info in sendto() call. We have to do a connect(udp_sock, endpoint_info) first and then invoke sendto(). This works. But the question is how can I influence the source port of these packets? Thanks, -Nataraj -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14057): https://lists.fd.io/g/vpp-dev/message/14057 Mute This Topic: https://lists.fd.io/mt/34294099/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Question regarding NAT44 endpoint-dependent
Hi all,
I am trouble with endpoint-dependent NAT. I am running out of tcp
connections. Also, sessions are not deleted after the NAT timeout period.
Number of sessions remain almost the same every after no usage for a day or
so.
Here are the stats, nat config and timeouts:
https://gist.github.com/ironpillow/5512e23831827eaf12a6295c0be9b3c8
startup.conf
nat {
translation hash buckets 1048576
translation hash memory 268435456
user hash buckets 250
max translations per user 2
endpoint-dependent
}
vpp# sh nat timeouts
udp timeout: 300sec
tcp-established timeout: 7440sec
tcp-transitory timeout: 240sec
icmp timeout: 60sec
In the above link you can see the nat44 sessions, total tcp and udp
sessions and hash tables.
Let me know if you need more logs or info.
Any advice?
Thanks!
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14055): https://lists.fd.io/g/vpp-dev/message/14055
Mute This Topic: https://lists.fd.io/mt/34291952/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] FD.io Nexus Maintenance: 2019-09-25 1700 UTC to 2100 UTC
Starting maintenance On 09/25/2019 11:02 AM, Vanessa Valderrama wrote: > > Jenkins has been placed in shut down mode to prepare for maintenance. > > > On 09/23/2019 04:08 PM, Vanessa Valderrama wrote: >> >> *What:* >> >> LF will performing maintenance on the Nexus server to migrate data to >> two new SSD volumes in attempt to resolve the intermittent issue with >> hung jobs we are experiencing >> >> * Migrate Nexus data to new volumes >> >> *When:* >> 2019-09-25 1700 UTC to 2100 UTC * >> ** >> Impact:* We will place Jenkins in shutdown mode at 1600 UTC. Jobs >> will be aborted at 1700 UTC >> Jenkins and Nexus will be unavailable during this time >> >> You can subscribe to status updates here: >> https://fdio.statuspage.io/incidents/f5tfpfdyd8l0 >> >> > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14054): https://lists.fd.io/g/vpp-dev/message/14054 Mute This Topic: https://lists.fd.io/mt/34269004/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] FD.io Nexus Maintenance: 2019-09-25 1700 UTC to 2100 UTC
Jenkins has been placed in shut down mode to prepare for maintenance. On 09/23/2019 04:08 PM, Vanessa Valderrama wrote: > > *What:* > > LF will performing maintenance on the Nexus server to migrate data to > two new SSD volumes in attempt to resolve the intermittent issue with > hung jobs we are experiencing > > * Migrate Nexus data to new volumes > > *When:* > 2019-09-25 1700 UTC to 2100 UTC * > ** > Impact:* We will place Jenkins in shutdown mode at 1600 UTC. Jobs will > be aborted at 1700 UTC > Jenkins and Nexus will be unavailable during this time > > You can subscribe to status updates here: > https://fdio.statuspage.io/incidents/f5tfpfdyd8l0 > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14053): https://lists.fd.io/g/vpp-dev/message/14053 Mute This Topic: https://lists.fd.io/mt/34269004/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] accessing object pools from multiple threads
git grep ‘!am->is_mp_safe’ --a > On 25 Sep 2019, at 10:24, Satya Murthy wrote: > > Thanks Andrew for the quick reply. > Can you please point me to the code where the barrier lock is getting applied > for acls. > > -- > Thanks & Regards, > Murthy > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#14051): https://lists.fd.io/g/vpp-dev/message/14051 > Mute This Topic: https://lists.fd.io/mt/34285184/675608 > Group Owner: vpp-dev+ow...@lists.fd.io > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [ayour...@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14052): https://lists.fd.io/g/vpp-dev/message/14052 Mute This Topic: https://lists.fd.io/mt/34285184/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] accessing object pools from multiple threads
Thanks Andrew for the quick reply. Can you please point me to the code where the barrier lock is getting applied for acls. -- Thanks & Regards, Murthy -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14051): https://lists.fd.io/g/vpp-dev/message/14051 Mute This Topic: https://lists.fd.io/mt/34285184/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] accessing object pools from multiple threads
Yes, ACL update messages are not marked as Mp-safe, consequently are subject to barrier lock, thus we can use this pool in this way. Pools are *not* thread safe, which is why for example the session pools for reflexive acl processing are per-thread (see acl_fa_per_worker_data_t structure). --a > On 25 Sep 2019, at 08:24, Satya Murthy wrote: > > Hi , > > I have a basic question on how object pools are accessed by multiple threads > in VPP. Do we have any locks underlying that safe gaurd the object pools ? > > For example: > In acl_main_t, we have a pool of acl lists as below. > acl_list_t *acls; /* Pool of ACLs */ > > This list will be populated by vpp main_thread for add/del. > Also, this list will be accessed by worker thread during packet processing. > > So, is this list guarded by any lock at lower layers for synchronizing the > access between main thread and worker thread ? > > Thanks & Regards, > Satish > > > -- > Thanks & Regards, > Murthy > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#14049): https://lists.fd.io/g/vpp-dev/message/14049 > Mute This Topic: https://lists.fd.io/mt/34285184/675608 > Group Owner: vpp-dev+ow...@lists.fd.io > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [ayour...@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14050): https://lists.fd.io/g/vpp-dev/message/14050 Mute This Topic: https://lists.fd.io/mt/34285184/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] accessing object pools from multiple threads
Hi , I have a basic question on how object pools are accessed by multiple threads in VPP. Do we have any locks underlying that safe gaurd the object pools ? For example: In acl_main_t, we have a pool of acl lists as below. *acl_list_t *acls; /* Pool of ACLs */* This list will be populated by vpp main_thread for add/del. Also, this list will be accessed by worker thread during packet processing. So, is this list guarded by any lock at lower layers for synchronizing the access between main thread and worker thread ? Thanks & Regards, Satish -- Thanks & Regards, Murthy -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14049): https://lists.fd.io/g/vpp-dev/message/14049 Mute This Topic: https://lists.fd.io/mt/34285184/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
