Re: UDP Lite support
Joe Nosay wrote: On Mon, Mar 31, 2014 at 10:20 PM, Kevin Lo ke...@freebsd.org wrote: On 2014/03/28 00:21, John Baldwin wrote: On Thursday, March 27, 2014 5:32:16 am Kevin Lo wrote: Are you interested in working on these and report back? The revised patch is available at: http://people.freebsd.org/~kevlo/udplite.diff Thank you for your suggestions. A few suggestions: - I would just drop the INP lock and return EOPNOTSUPP directly rather than using goto's to 'bad_setoptname' and 'bad_getoptname' so the UDP-lite options are self-contained. Fixed. Thanks. - I'm not a super big fan of all the udp_common_* macros only because I think it obfuscates things. At the very least, please move these things out of the header and into udp_usrreq.c so they are closer to the implementation. I would even suggest making them inline functions instead of macros. Okay, I removed two udp_common_* macros. I also renamed udp_common_init() to udp_udplite_init() and moved it into udp_usrreq.c. Using a macro here to follow the style used in SCTP (sctp_os_bsd.h). Here's a third version of the udp-lite patch: http://people.freebsd.org/~kevlo/udplite.diff Ok, I would say that udp_common_init() is actually a better name if you keep the macro (which I think is fine) rather than udp_udplite_init() as the macro is not specific to UDP Lite. However, thanks for moving the macros out of the header. Thank you John. glebius@ suggests we don't need to have two absolutely equal uma zones since most systems don't run UDP-Lite. If practice shows that a differentiation at zone level between UDP and UDP-Lite PCBs is important, then it could be done later. Following up with a fourth version of the udp-lite patch. http://people.freebsd.org/~kevlo/udplite.diff On top of the previous versions, this: - removes a uma zone for udp-lite - udp_common_ctlinput() belongs under #ifdef INET - removes sysctl nodes for udp-lite. - bumps version and adds my copyright. Kevin Do I patch over the current src- which was already patched with version 3- or do I just start new? Start new, thanks. Kevin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On Monday, March 31, 2014 10:20:53 pm Kevin Lo wrote: On 2014/03/28 00:21, John Baldwin wrote: On Thursday, March 27, 2014 5:32:16 am Kevin Lo wrote: Are you interested in working on these and report back? The revised patch is available at: http://people.freebsd.org/~kevlo/udplite.diff Thank you for your suggestions. A few suggestions: - I would just drop the INP lock and return EOPNOTSUPP directly rather than using goto's to 'bad_setoptname' and 'bad_getoptname' so the UDP-lite options are self-contained. Fixed. Thanks. - I'm not a super big fan of all the udp_common_* macros only because I think it obfuscates things. At the very least, please move these things out of the header and into udp_usrreq.c so they are closer to the implementation. I would even suggest making them inline functions instead of macros. Okay, I removed two udp_common_* macros. I also renamed udp_common_init() to udp_udplite_init() and moved it into udp_usrreq.c. Using a macro here to follow the style used in SCTP (sctp_os_bsd.h). Here's a third version of the udp-lite patch: http://people.freebsd.org/~kevlo/udplite.diff Ok, I would say that udp_common_init() is actually a better name if you keep the macro (which I think is fine) rather than udp_udplite_init() as the macro is not specific to UDP Lite. However, thanks for moving the macros out of the header. Thank you John. glebius@ suggests we don't need to have two absolutely equal uma zones since most systems don't run UDP-Lite. If practice shows that a differentiation at zone level between UDP and UDP-Lite PCBs is important, then it could be done later. Ok. I do think this is probably cleaner as well and almost suggested it myself. The only caveat to this is that it means UDP and UDP Lite sockets share the same resource limit. That is probably fine in practice. I think the current patch looks good. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Re: UDP Lite support
Hi! On 31 March 2014 19:20, Kevin Lo ke...@freebsd.org wrote: Thank you John. glebius@ suggests we don't need to have two absolutely equal uma zones since most systems don't run UDP-Lite. If practice shows that a differentiation at zone level between UDP and UDP-Lite PCBs is important, then it could be done later. Following up with a fourth version of the udp-lite patch. http://people.freebsd.org/~kevlo/udplite.diff On top of the previous versions, this: - removes a uma zone for udp-lite - udp_common_ctlinput() belongs under #ifdef INET - removes sysctl nodes for udp-lite. - bumps version and adds my copyright. I've just briefly review this. I recommend turning the places where you do this: + pcbinfo = (pr == IPPROTO_UDP) ? V_udbinfo : V_ulitecbinfo; .. into some inline function which returns the correct pcbinfo based on what 'pr' is. That way if someone wants to add another derivative UDP handler they won't have to go and change those conditionals to yet another set of nested conditionals. Same for: + pcblist = (pr == IPPROTO_UDP) ? V_udb : V_ulitecb; Other than that, it looks good. -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On 2014/04/02 04:53, Adrian Chadd wrote: Hi! Hi Adrian, On 31 March 2014 19:20, Kevin Lo ke...@freebsd.org wrote: Thank you John. glebius@ suggests we don't need to have two absolutely equal uma zones since most systems don't run UDP-Lite. If practice shows that a differentiation at zone level between UDP and UDP-Lite PCBs is important, then it could be done later. Following up with a fourth version of the udp-lite patch. http://people.freebsd.org/~kevlo/udplite.diff On top of the previous versions, this: - removes a uma zone for udp-lite - udp_common_ctlinput() belongs under #ifdef INET - removes sysctl nodes for udp-lite. - bumps version and adds my copyright. I've just briefly review this. I recommend turning the places where you do this: + pcbinfo = (pr == IPPROTO_UDP) ? V_udbinfo : V_ulitecbinfo; .. into some inline function which returns the correct pcbinfo based on what 'pr' is. That way if someone wants to add another derivative UDP handler they won't have to go and change those conditionals to yet another set of nested conditionals. Same for: + pcblist = (pr == IPPROTO_UDP) ? V_udb : V_ulitecb; Other than that, it looks good. Thanks for the review. I added two inline functions get_inpcbinfo() and get_pcblist() which return the correct pcbinfo and pcblist respectively. The current version of the patch is in the same location, thanks. -a Kevin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Re: UDP Lite support
On 2014/03/28 00:21, John Baldwin wrote: On Thursday, March 27, 2014 5:32:16 am Kevin Lo wrote: Are you interested in working on these and report back? The revised patch is available at: http://people.freebsd.org/~kevlo/udplite.diff Thank you for your suggestions. A few suggestions: - I would just drop the INP lock and return EOPNOTSUPP directly rather than using goto's to 'bad_setoptname' and 'bad_getoptname' so the UDP-lite options are self-contained. Fixed. Thanks. - I'm not a super big fan of all the udp_common_* macros only because I think it obfuscates things. At the very least, please move these things out of the header and into udp_usrreq.c so they are closer to the implementation. I would even suggest making them inline functions instead of macros. Okay, I removed two udp_common_* macros. I also renamed udp_common_init() to udp_udplite_init() and moved it into udp_usrreq.c. Using a macro here to follow the style used in SCTP (sctp_os_bsd.h). Here's a third version of the udp-lite patch: http://people.freebsd.org/~kevlo/udplite.diff Ok, I would say that udp_common_init() is actually a better name if you keep the macro (which I think is fine) rather than udp_udplite_init() as the macro is not specific to UDP Lite. However, thanks for moving the macros out of the header. Thank you John. glebius@ suggests we don't need to have two absolutely equal uma zones since most systems don't run UDP-Lite. If practice shows that a differentiation at zone level between UDP and UDP-Lite PCBs is important, then it could be done later. Following up with a fourth version of the udp-lite patch. http://people.freebsd.org/~kevlo/udplite.diff On top of the previous versions, this: - removes a uma zone for udp-lite - udp_common_ctlinput() belongs under #ifdef INET - removes sysctl nodes for udp-lite. - bumps version and adds my copyright. Kevin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Re: UDP Lite support
On Mon, Mar 31, 2014 at 10:20 PM, Kevin Lo ke...@freebsd.org wrote: On 2014/03/28 00:21, John Baldwin wrote: On Thursday, March 27, 2014 5:32:16 am Kevin Lo wrote: Are you interested in working on these and report back? The revised patch is available at: http://people.freebsd.org/~kevlo/udplite.diff Thank you for your suggestions. A few suggestions: - I would just drop the INP lock and return EOPNOTSUPP directly rather than using goto's to 'bad_setoptname' and 'bad_getoptname' so the UDP-lite options are self-contained. Fixed. Thanks. - I'm not a super big fan of all the udp_common_* macros only because I think it obfuscates things. At the very least, please move these things out of the header and into udp_usrreq.c so they are closer to the implementation. I would even suggest making them inline functions instead of macros. Okay, I removed two udp_common_* macros. I also renamed udp_common_init() to udp_udplite_init() and moved it into udp_usrreq.c. Using a macro here to follow the style used in SCTP (sctp_os_bsd.h). Here's a third version of the udp-lite patch: http://people.freebsd.org/~kevlo/udplite.diff Ok, I would say that udp_common_init() is actually a better name if you keep the macro (which I think is fine) rather than udp_udplite_init() as the macro is not specific to UDP Lite. However, thanks for moving the macros out of the header. Thank you John. glebius@ suggests we don't need to have two absolutely equal uma zones since most systems don't run UDP-Lite. If practice shows that a differentiation at zone level between UDP and UDP-Lite PCBs is important, then it could be done later. Following up with a fourth version of the udp-lite patch. http://people.freebsd.org/~kevlo/udplite.diff On top of the previous versions, this: - removes a uma zone for udp-lite - udp_common_ctlinput() belongs under #ifdef INET - removes sysctl nodes for udp-lite. - bumps version and adds my copyright. Kevin Do I patch over the current src- which was already patched with version 3- or do I just start new? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On 2014/03/26 23:22, John Baldwin wrote: On Friday, March 21, 2014 3:38:19 am Kevin Lo wrote: On 2014/03/03 04:08, Xin Li wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 3/2/14, 10:42 AM, Joe Nosay wrote: On Thu, Feb 27, 2014 at 3:22 AM, Joe Nosay superbisq...@gmail.com wrote: On Wed, Feb 26, 2014 at 11:19 PM, Xin Li delp...@delphij.net wrote: On 02/26/14 18:52, Joe Nosay wrote: On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis bro...@freebsd.org wrote: On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks Thanks. I will ask kevlo and maybe bring it up on freebsd-net. It has to do with an implementation of the JACK server using UDP Lite for transferring data. http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html Looks like nobody proposed a patch? I think the concern was that this is not very useful in real-world scenarios due to link layer error detection mechanism but that doesn't raise a red flag to me assuming this is sufficiently self contained feature as it would improve compatibility with other operating systems. Cheers, https://github.com/torelizer/jack_trauma Not my project; but, I want to port it to FreeBSD. First is to get it to build from source. Use your raspberry pi with FreeBSD to broadcast your tunes and all. Thanks for all of the input. The project is being reworked to improve the code. Kevin Lo have a patchset but needs someone to do performance testing (its impact on non-UDPLite applications), test with vimage, etc: http://people.freebsd.org/~kevlo/udplite.diff http://people.freebsd.org/~kevlo/udp-v.diff Are you interested in working on these and report back? The revised patch is available at: http://people.freebsd.org/~kevlo/udplite.diff Thank you for your suggestions. A few suggestions: - I would just drop the INP lock and return EOPNOTSUPP directly rather than using goto's to 'bad_setoptname' and 'bad_getoptname' so the UDP-lite options are self-contained. Fixed. - I'm not a super big fan of all the udp_common_* macros only because I think it obfuscates things. At the very least, please move these things out of the header and into udp_usrreq.c so they are closer to the implementation. I would even suggest making them inline functions instead of macros. Okay, I removed two udp_common_* macros. I also renamed udp_common_init() to udp_udplite_init() and moved it into udp_usrreq.c. Using a macro here to follow the style used in SCTP (sctp_os_bsd.h). Here's a third version of the udp-lite patch: http://people.freebsd.org/~kevlo/udplite.diff However, I think the patch generally looks ok. Cool! Thanks again for your review of udp-lite's patch :-) Kevin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On Thursday, March 27, 2014 5:32:16 am Kevin Lo wrote: Are you interested in working on these and report back? The revised patch is available at: http://people.freebsd.org/~kevlo/udplite.diff Thank you for your suggestions. A few suggestions: - I would just drop the INP lock and return EOPNOTSUPP directly rather than using goto's to 'bad_setoptname' and 'bad_getoptname' so the UDP-lite options are self-contained. Fixed. Thanks. - I'm not a super big fan of all the udp_common_* macros only because I think it obfuscates things. At the very least, please move these things out of the header and into udp_usrreq.c so they are closer to the implementation. I would even suggest making them inline functions instead of macros. Okay, I removed two udp_common_* macros. I also renamed udp_common_init() to udp_udplite_init() and moved it into udp_usrreq.c. Using a macro here to follow the style used in SCTP (sctp_os_bsd.h). Here's a third version of the udp-lite patch: http://people.freebsd.org/~kevlo/udplite.diff Ok, I would say that udp_common_init() is actually a better name if you keep the macro (which I think is fine) rather than udp_udplite_init() as the macro is not specific to UDP Lite. However, thanks for moving the macros out of the header. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On Friday, March 21, 2014 3:38:19 am Kevin Lo wrote: On 2014/03/03 04:08, Xin Li wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 3/2/14, 10:42 AM, Joe Nosay wrote: On Thu, Feb 27, 2014 at 3:22 AM, Joe Nosay superbisq...@gmail.com wrote: On Wed, Feb 26, 2014 at 11:19 PM, Xin Li delp...@delphij.net wrote: On 02/26/14 18:52, Joe Nosay wrote: On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis bro...@freebsd.org wrote: On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks Thanks. I will ask kevlo and maybe bring it up on freebsd-net. It has to do with an implementation of the JACK server using UDP Lite for transferring data. http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html Looks like nobody proposed a patch? I think the concern was that this is not very useful in real-world scenarios due to link layer error detection mechanism but that doesn't raise a red flag to me assuming this is sufficiently self contained feature as it would improve compatibility with other operating systems. Cheers, https://github.com/torelizer/jack_trauma Not my project; but, I want to port it to FreeBSD. First is to get it to build from source. Use your raspberry pi with FreeBSD to broadcast your tunes and all. Thanks for all of the input. The project is being reworked to improve the code. Kevin Lo have a patchset but needs someone to do performance testing (its impact on non-UDPLite applications), test with vimage, etc: http://people.freebsd.org/~kevlo/udplite.diff http://people.freebsd.org/~kevlo/udp-v.diff Are you interested in working on these and report back? The revised patch is available at: http://people.freebsd.org/~kevlo/udplite.diff A few suggestions: - I would just drop the INP lock and return EOPNOTSUPP directly rather than using goto's to 'bad_setoptname' and 'bad_getoptname' so the UDP-lite options are self-contained. - I'm not a super big fan of all the udp_common_* macros only because I think it obfuscates things. At the very least, please move these things out of the header and into udp_usrreq.c so they are closer to the implementation. I would even suggest making them inline functions instead of macros. However, I think the patch generally looks ok. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Re: UDP Lite support
On 2014/03/03 04:08, Xin Li wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 3/2/14, 10:42 AM, Joe Nosay wrote:
On Thu, Feb 27, 2014 at 3:22 AM, Joe Nosay superbisq...@gmail.com
wrote:
On Wed, Feb 26, 2014 at 11:19 PM, Xin Li delp...@delphij.net
wrote:
On 02/26/14 18:52, Joe Nosay wrote:
On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis
bro...@freebsd.org wrote:
On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay
wrote:
The last thread on this was in 2006. Has it ever been
reconsidered or is the likelihood of too many damaged
packets the reason for not supporting? I'm not sure
where to put this question. Apologies for the noise.
You've provided next to no context. What is the
question? What thread are you referring to? If this is
the usual UDP then freebsd-net would be vastly more
appropriate than -current.
-- Brooks
Thanks. I will ask kevlo and maybe bring it up on
freebsd-net. It has to do with an implementation of the
JACK server using UDP Lite for transferring data.
http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html
Looks
like nobody proposed a patch?
I think the concern was that this is not very useful in real-world
scenarios due to link layer error detection mechanism but that
doesn't raise a red flag to me assuming this is sufficiently self
contained feature as it would improve compatibility with other
operating systems.
Cheers,
https://github.com/torelizer/jack_trauma
Not my project; but, I want to port it to FreeBSD. First is to
get it to build from source. Use your raspberry pi with FreeBSD
to broadcast your tunes and all.
Thanks for all of the input. The project is being reworked to
improve the code.
Kevin Lo have a patchset but needs someone to do performance testing
(its impact on non-UDPLite applications), test with vimage, etc:
http://people.freebsd.org/~kevlo/udplite.diff
http://people.freebsd.org/~kevlo/udp-v.diff
Are you interested in working on these and report back?
The revised patch is available at:
http://people.freebsd.org/~kevlo/udplite.diff
I measure and compare the performance of UDP with/without UDP-lite patch,
the udp-lite patch doesn't affect the performance.
Tested system is FreeBSD/amd64 -CURRENT(r263301), machines were connected
via cross-link cable.
Machines:
-
Dragon (connected to Monkey)
CPU: Intel(R) Core(TM) i3-2330E CPU @ 2.20GHz (2195.06-MHz K8-class CPU)
Origin=GenuineIntel Id=0x206a7 Family=0x6 Model=0x2a Stepping=7
RAM: 2GB
NIC: on-board em(4)
Monkey (connected to Dragon)
CPU: Intel(R) Core(TM) i3-2330E CPU @ 2.20GHz (2195.06-MHz K8-class CPU)
Origin=GenuineIntel Id=0x206a7 Family=0x6 Model=0x2a Stepping=7
RAM: 1GB
NIC: on-board em(4)
Monkey runs 'netserver'.
All tests done with netperf software:
UDP Stream test:
-
% netperf -c -l 60 -H Monkey -t UDP_STREAM -i 10,2 -I 99,5 -- -m 64 -s
57344 -S 57344
% netperf -c -l 60 -H Monkey -t UDP_STREAM -i 10,2 -I 99,5 -- -m 4096 -s
57344 -S 57344
% netperf -c -l 60 -H Monkey -t UDP_STREAM -i 10,2 -I 99,5 -- -m 16384
-s 57344 -S 57344
Without UDP-Lite patch:
Netperf test MTU BW BSIZE
-- --
UDP_STREAM 1500 211.3 64
UDP_STREAM 1500 950.4 4096
UDP_STREAM 1500 948.616384
With UDP-Lite patch:
Netperf test MTU BW BSIZE
-- --
UDP_STREAM 1500 216.5 64
UDP_STREAM 1500 950.3 4096
UDP_STREAM 1500 948.616384
Cheers,
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJTE4+mAAoJEJW2GBstM+nsthoQAIW67l7yDfIPvxDsNIWWJcRd
8brFYCAOPYE4LpuLGjtSgy370aBe9JmwAm41tE4qF0WhGpcu6TLsKjgMGWa/lHCc
JId8+WBfbbQT8XJj/d+3oOETn5/rglvlRhJbnNIwaQpTXxuMC5oz2nGW7rIpIkaA
OHo0D20DzGj4nxrQvijZ7DsMkk3F+KJu/4p7M6lpsIPCakknW1WD7IHRfbZ4Oldz
2xH4HfIk7cAdA7i/YUNjlpSgWFQ5OU03J5HAYfC6W37wiGbjdBYf/PKVhJ8hz7+D
OCl+yCV00u4fCjlY6zXFea9pGr7Cl1P+sapwKDZ4g+NpNHxBUVY+ahbjQUHYON2W
sdzAsLpMMqavCr1o8mcXdm7IPRlLUK9QZUySC9DitPvoF8G2llTAz1mWa4/Oj7/S
JMiUERcaL5gdFN8EgEKkamFgLJguYquAjGtiowa51EMbnZG0Q2yWUcrEBFHWBEZT
RW1u6r4ChIrPE9X5ljfFpQyKG6jFhYFXG+iVlgTB7F2ZWhjPAXi/tLbBnvIcci1m
Md4XFm/bBJj/yNXdPuCi+CtvvdpZ/d4LQn4B7By5bIo1QjCb4Zx5n2Tq5xnYZUOI
CnSVnNSkwLbbrAVtYOVWnrSuwR33JQnqeGHdM+XYBBwKBRhrx+ZgFWD7N6Gm95PU
xXSxkgYVXI4sgi7Lh3Ia
=2Vmc
-END PGP SIGNATURE-
Kevin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On Sun, Mar 2, 2014 at 4:23 PM, Joe Nosay superbisq...@gmail.com wrote: On Sun, Mar 2, 2014 at 4:04 PM, Joe Nosay superbisq...@gmail.com wrote: On Sun, Mar 2, 2014 at 3:20 PM, Joe Nosay superbisq...@gmail.com wrote: On Sun, Mar 2, 2014 at 3:19 PM, Joe Nosay superbisq...@gmail.comwrote: On Sun, Mar 2, 2014 at 3:08 PM, Xin Li delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 3/2/14, 10:42 AM, Joe Nosay wrote: On Thu, Feb 27, 2014 at 3:22 AM, Joe Nosay superbisq...@gmail.com wrote: On Wed, Feb 26, 2014 at 11:19 PM, Xin Li delp...@delphij.net wrote: On 02/26/14 18:52, Joe Nosay wrote: On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis bro...@freebsd.org wrote: On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks Thanks. I will ask kevlo and maybe bring it up on freebsd-net. It has to do with an implementation of the JACK server using UDP Lite for transferring data. http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html Looks like nobody proposed a patch? I think the concern was that this is not very useful in real-world scenarios due to link layer error detection mechanism but that doesn't raise a red flag to me assuming this is sufficiently self contained feature as it would improve compatibility with other operating systems. Cheers, https://github.com/torelizer/jack_trauma Not my project; but, I want to port it to FreeBSD. First is to get it to build from source. Use your raspberry pi with FreeBSD to broadcast your tunes and all. Thanks for all of the input. The project is being reworked to improve the code. Kevin Lo have a patchset but needs someone to do performance testing (its impact on non-UDPLite applications), test with vimage, etc: http://people.freebsd.org/~kevlo/udplite.diff http://people.freebsd.org/~kevlo/udp-v.diff Are you interested in working on these and report back? Cheers, -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJTE4+mAAoJEJW2GBstM+nsthoQAIW67l7yDfIPvxDsNIWWJcRd 8brFYCAOPYE4LpuLGjtSgy370aBe9JmwAm41tE4qF0WhGpcu6TLsKjgMGWa/lHCc JId8+WBfbbQT8XJj/d+3oOETn5/rglvlRhJbnNIwaQpTXxuMC5oz2nGW7rIpIkaA OHo0D20DzGj4nxrQvijZ7DsMkk3F+KJu/4p7M6lpsIPCakknW1WD7IHRfbZ4Oldz 2xH4HfIk7cAdA7i/YUNjlpSgWFQ5OU03J5HAYfC6W37wiGbjdBYf/PKVhJ8hz7+D OCl+yCV00u4fCjlY6zXFea9pGr7Cl1P+sapwKDZ4g+NpNHxBUVY+ahbjQUHYON2W sdzAsLpMMqavCr1o8mcXdm7IPRlLUK9QZUySC9DitPvoF8G2llTAz1mWa4/Oj7/S JMiUERcaL5gdFN8EgEKkamFgLJguYquAjGtiowa51EMbnZG0Q2yWUcrEBFHWBEZT RW1u6r4ChIrPE9X5ljfFpQyKG6jFhYFXG+iVlgTB7F2ZWhjPAXi/tLbBnvIcci1m Md4XFm/bBJj/yNXdPuCi+CtvvdpZ/d4LQn4B7By5bIo1QjCb4Zx5n2Tq5xnYZUOI CnSVnNSkwLbbrAVtYOVWnrSuwR33JQnqeGHdM+XYBBwKBRhrx+ZgFWD7N6Gm95PU xXSxkgYVXI4sgi7Lh3Ia =2Vmc -END PGP SIGNATURE- I have on patch file that Lo sent. Three different files are on it with the assumption that the patch-root is /usr/src. I'm thinking about snipping it twice and then applying each subpatch within the proper subdirectory. Now, this would not when Index:reference is at the header of each, right? One not one in first sentence. Insert hurt between not when in last sentence. I'm doing patch -p *.diff and the process is taking some time. What am I doing wrong? Syntax. Rebuild reinstall the source portions in common then find an application that uses udplite, right? Du. Thanks. Yuhhh There is x264 and wireshark as my available options for testing if udp lite works. Give me a moment because I have a single machine and need to setup a virtual graphics card. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On Thu, Feb 27, 2014 at 3:22 AM, Joe Nosay superbisq...@gmail.com wrote: On Wed, Feb 26, 2014 at 11:19 PM, Xin Li delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/26/14 18:52, Joe Nosay wrote: On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis bro...@freebsd.org wrote: On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks Thanks. I will ask kevlo and maybe bring it up on freebsd-net. It has to do with an implementation of the JACK server using UDP Lite for transferring data. http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html Looks like nobody proposed a patch? I think the concern was that this is not very useful in real-world scenarios due to link layer error detection mechanism but that doesn't raise a red flag to me assuming this is sufficiently self contained feature as it would improve compatibility with other operating systems. Cheers, - -- Xin LI delp...@delphij.nethttps://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCgAGBQJTDrzbAAoJEJW2GBstM+nsJVoP/29XRcleHMnAVa1UOG0+CD2y 0e/pAmk5vay599gjmiKSAuTSeKNaawRF3FZP+QsxhKw/lNTYEHlppUw7FDc01NqO pk1GsIu+mVuLlzZBNSuAkXdMMzJz5OKfY9GeK7Uw4iumiNP5LKpoC1RaYqLVASGf JH6tqJdSVnD+apWxV/PF4orCXZECFLkQZhbgZe+2nni+te6OfzIbkjhBqn8ZIDNY m9GbYwkTEATBDcMGgl9F0wBfcLhQLF4p4+TnsCguP0HAbxCtbZmt3SXe6Xt4y2YE iHlO/qstGKrl61aiehtpasjiljJaN5ucmuv8XDGbix4cghiJCJAGmxXGxCoHs/Uq vkn88wfV901pjYWPWf9HmTdjSmsck0k2+srWYlJuRymVKvMsL2mwPky+QL9SZ6MY NJ8kXUl5szFwdN4OtO+1iUvVZNLkVDlV5bmnc5KOkciFRoLuTq1/f/xzGj/YDZpx 2DxjddVyvJ6YhrUSSAGoOcdxIpDejKfVif0ANoocsKLAnTHtNxdB76doJH4wBl+W LAl9a9IqVOiefFe9qb6tZky3lft3HUe4XvLJPraKTfbvA9VAKPqZbc2Z8eeoqb49 LPC2n8WnlnaXB9KXKSWTLXbdcY2L+HnAt2+DEv4viSyKSXQg00aEbm+R95h1pTz7 oMv/8VGg5akyRQtkTTIx =ukUF -END PGP SIGNATURE- https://github.com/torelizer/jack_trauma Not my project; but, I want to port it to FreeBSD. First is to get it to build from source. Use your raspberry pi with FreeBSD to broadcast your tunes and all. Thanks for all of the input. The project is being reworked to improve the code. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 3/2/14, 10:42 AM, Joe Nosay wrote: On Thu, Feb 27, 2014 at 3:22 AM, Joe Nosay superbisq...@gmail.com wrote: On Wed, Feb 26, 2014 at 11:19 PM, Xin Li delp...@delphij.net wrote: On 02/26/14 18:52, Joe Nosay wrote: On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis bro...@freebsd.org wrote: On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks Thanks. I will ask kevlo and maybe bring it up on freebsd-net. It has to do with an implementation of the JACK server using UDP Lite for transferring data. http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html Looks like nobody proposed a patch? I think the concern was that this is not very useful in real-world scenarios due to link layer error detection mechanism but that doesn't raise a red flag to me assuming this is sufficiently self contained feature as it would improve compatibility with other operating systems. Cheers, https://github.com/torelizer/jack_trauma Not my project; but, I want to port it to FreeBSD. First is to get it to build from source. Use your raspberry pi with FreeBSD to broadcast your tunes and all. Thanks for all of the input. The project is being reworked to improve the code. Kevin Lo have a patchset but needs someone to do performance testing (its impact on non-UDPLite applications), test with vimage, etc: http://people.freebsd.org/~kevlo/udplite.diff http://people.freebsd.org/~kevlo/udp-v.diff Are you interested in working on these and report back? Cheers, -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJTE4+mAAoJEJW2GBstM+nsthoQAIW67l7yDfIPvxDsNIWWJcRd 8brFYCAOPYE4LpuLGjtSgy370aBe9JmwAm41tE4qF0WhGpcu6TLsKjgMGWa/lHCc JId8+WBfbbQT8XJj/d+3oOETn5/rglvlRhJbnNIwaQpTXxuMC5oz2nGW7rIpIkaA OHo0D20DzGj4nxrQvijZ7DsMkk3F+KJu/4p7M6lpsIPCakknW1WD7IHRfbZ4Oldz 2xH4HfIk7cAdA7i/YUNjlpSgWFQ5OU03J5HAYfC6W37wiGbjdBYf/PKVhJ8hz7+D OCl+yCV00u4fCjlY6zXFea9pGr7Cl1P+sapwKDZ4g+NpNHxBUVY+ahbjQUHYON2W sdzAsLpMMqavCr1o8mcXdm7IPRlLUK9QZUySC9DitPvoF8G2llTAz1mWa4/Oj7/S JMiUERcaL5gdFN8EgEKkamFgLJguYquAjGtiowa51EMbnZG0Q2yWUcrEBFHWBEZT RW1u6r4ChIrPE9X5ljfFpQyKG6jFhYFXG+iVlgTB7F2ZWhjPAXi/tLbBnvIcci1m Md4XFm/bBJj/yNXdPuCi+CtvvdpZ/d4LQn4B7By5bIo1QjCb4Zx5n2Tq5xnYZUOI CnSVnNSkwLbbrAVtYOVWnrSuwR33JQnqeGHdM+XYBBwKBRhrx+ZgFWD7N6Gm95PU xXSxkgYVXI4sgi7Lh3Ia =2Vmc -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On Sun, Mar 2, 2014 at 3:08 PM, Xin Li delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 3/2/14, 10:42 AM, Joe Nosay wrote: On Thu, Feb 27, 2014 at 3:22 AM, Joe Nosay superbisq...@gmail.com wrote: On Wed, Feb 26, 2014 at 11:19 PM, Xin Li delp...@delphij.net wrote: On 02/26/14 18:52, Joe Nosay wrote: On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis bro...@freebsd.org wrote: On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks Thanks. I will ask kevlo and maybe bring it up on freebsd-net. It has to do with an implementation of the JACK server using UDP Lite for transferring data. http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html Looks like nobody proposed a patch? I think the concern was that this is not very useful in real-world scenarios due to link layer error detection mechanism but that doesn't raise a red flag to me assuming this is sufficiently self contained feature as it would improve compatibility with other operating systems. Cheers, https://github.com/torelizer/jack_trauma Not my project; but, I want to port it to FreeBSD. First is to get it to build from source. Use your raspberry pi with FreeBSD to broadcast your tunes and all. Thanks for all of the input. The project is being reworked to improve the code. Kevin Lo have a patchset but needs someone to do performance testing (its impact on non-UDPLite applications), test with vimage, etc: http://people.freebsd.org/~kevlo/udplite.diff http://people.freebsd.org/~kevlo/udp-v.diff Are you interested in working on these and report back? Cheers, -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJTE4+mAAoJEJW2GBstM+nsthoQAIW67l7yDfIPvxDsNIWWJcRd 8brFYCAOPYE4LpuLGjtSgy370aBe9JmwAm41tE4qF0WhGpcu6TLsKjgMGWa/lHCc JId8+WBfbbQT8XJj/d+3oOETn5/rglvlRhJbnNIwaQpTXxuMC5oz2nGW7rIpIkaA OHo0D20DzGj4nxrQvijZ7DsMkk3F+KJu/4p7M6lpsIPCakknW1WD7IHRfbZ4Oldz 2xH4HfIk7cAdA7i/YUNjlpSgWFQ5OU03J5HAYfC6W37wiGbjdBYf/PKVhJ8hz7+D OCl+yCV00u4fCjlY6zXFea9pGr7Cl1P+sapwKDZ4g+NpNHxBUVY+ahbjQUHYON2W sdzAsLpMMqavCr1o8mcXdm7IPRlLUK9QZUySC9DitPvoF8G2llTAz1mWa4/Oj7/S JMiUERcaL5gdFN8EgEKkamFgLJguYquAjGtiowa51EMbnZG0Q2yWUcrEBFHWBEZT RW1u6r4ChIrPE9X5ljfFpQyKG6jFhYFXG+iVlgTB7F2ZWhjPAXi/tLbBnvIcci1m Md4XFm/bBJj/yNXdPuCi+CtvvdpZ/d4LQn4B7By5bIo1QjCb4Zx5n2Tq5xnYZUOI CnSVnNSkwLbbrAVtYOVWnrSuwR33JQnqeGHdM+XYBBwKBRhrx+ZgFWD7N6Gm95PU xXSxkgYVXI4sgi7Lh3Ia =2Vmc -END PGP SIGNATURE- I have on patch file that Lo sent. Three different files are on it with the assumption that the patch-root is /usr/src. I'm thinking about snipping it twice and then applying each subpatch within the proper subdirectory. Now, this would not when Index:reference is at the header of each, right? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On Sun, Mar 2, 2014 at 3:19 PM, Joe Nosay superbisq...@gmail.com wrote: On Sun, Mar 2, 2014 at 3:08 PM, Xin Li delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 3/2/14, 10:42 AM, Joe Nosay wrote: On Thu, Feb 27, 2014 at 3:22 AM, Joe Nosay superbisq...@gmail.com wrote: On Wed, Feb 26, 2014 at 11:19 PM, Xin Li delp...@delphij.net wrote: On 02/26/14 18:52, Joe Nosay wrote: On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis bro...@freebsd.org wrote: On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks Thanks. I will ask kevlo and maybe bring it up on freebsd-net. It has to do with an implementation of the JACK server using UDP Lite for transferring data. http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html Looks like nobody proposed a patch? I think the concern was that this is not very useful in real-world scenarios due to link layer error detection mechanism but that doesn't raise a red flag to me assuming this is sufficiently self contained feature as it would improve compatibility with other operating systems. Cheers, https://github.com/torelizer/jack_trauma Not my project; but, I want to port it to FreeBSD. First is to get it to build from source. Use your raspberry pi with FreeBSD to broadcast your tunes and all. Thanks for all of the input. The project is being reworked to improve the code. Kevin Lo have a patchset but needs someone to do performance testing (its impact on non-UDPLite applications), test with vimage, etc: http://people.freebsd.org/~kevlo/udplite.diff http://people.freebsd.org/~kevlo/udp-v.diff Are you interested in working on these and report back? Cheers, -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJTE4+mAAoJEJW2GBstM+nsthoQAIW67l7yDfIPvxDsNIWWJcRd 8brFYCAOPYE4LpuLGjtSgy370aBe9JmwAm41tE4qF0WhGpcu6TLsKjgMGWa/lHCc JId8+WBfbbQT8XJj/d+3oOETn5/rglvlRhJbnNIwaQpTXxuMC5oz2nGW7rIpIkaA OHo0D20DzGj4nxrQvijZ7DsMkk3F+KJu/4p7M6lpsIPCakknW1WD7IHRfbZ4Oldz 2xH4HfIk7cAdA7i/YUNjlpSgWFQ5OU03J5HAYfC6W37wiGbjdBYf/PKVhJ8hz7+D OCl+yCV00u4fCjlY6zXFea9pGr7Cl1P+sapwKDZ4g+NpNHxBUVY+ahbjQUHYON2W sdzAsLpMMqavCr1o8mcXdm7IPRlLUK9QZUySC9DitPvoF8G2llTAz1mWa4/Oj7/S JMiUERcaL5gdFN8EgEKkamFgLJguYquAjGtiowa51EMbnZG0Q2yWUcrEBFHWBEZT RW1u6r4ChIrPE9X5ljfFpQyKG6jFhYFXG+iVlgTB7F2ZWhjPAXi/tLbBnvIcci1m Md4XFm/bBJj/yNXdPuCi+CtvvdpZ/d4LQn4B7By5bIo1QjCb4Zx5n2Tq5xnYZUOI CnSVnNSkwLbbrAVtYOVWnrSuwR33JQnqeGHdM+XYBBwKBRhrx+ZgFWD7N6Gm95PU xXSxkgYVXI4sgi7Lh3Ia =2Vmc -END PGP SIGNATURE- I have on patch file that Lo sent. Three different files are on it with the assumption that the patch-root is /usr/src. I'm thinking about snipping it twice and then applying each subpatch within the proper subdirectory. Now, this would not when Index:reference is at the header of each, right? One not one in first sentence. Insert hurt between not when in last sentence. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On Sun, Mar 2, 2014 at 3:20 PM, Joe Nosay superbisq...@gmail.com wrote: On Sun, Mar 2, 2014 at 3:19 PM, Joe Nosay superbisq...@gmail.com wrote: On Sun, Mar 2, 2014 at 3:08 PM, Xin Li delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 3/2/14, 10:42 AM, Joe Nosay wrote: On Thu, Feb 27, 2014 at 3:22 AM, Joe Nosay superbisq...@gmail.com wrote: On Wed, Feb 26, 2014 at 11:19 PM, Xin Li delp...@delphij.net wrote: On 02/26/14 18:52, Joe Nosay wrote: On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis bro...@freebsd.org wrote: On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks Thanks. I will ask kevlo and maybe bring it up on freebsd-net. It has to do with an implementation of the JACK server using UDP Lite for transferring data. http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html Looks like nobody proposed a patch? I think the concern was that this is not very useful in real-world scenarios due to link layer error detection mechanism but that doesn't raise a red flag to me assuming this is sufficiently self contained feature as it would improve compatibility with other operating systems. Cheers, https://github.com/torelizer/jack_trauma Not my project; but, I want to port it to FreeBSD. First is to get it to build from source. Use your raspberry pi with FreeBSD to broadcast your tunes and all. Thanks for all of the input. The project is being reworked to improve the code. Kevin Lo have a patchset but needs someone to do performance testing (its impact on non-UDPLite applications), test with vimage, etc: http://people.freebsd.org/~kevlo/udplite.diff http://people.freebsd.org/~kevlo/udp-v.diff Are you interested in working on these and report back? Cheers, -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJTE4+mAAoJEJW2GBstM+nsthoQAIW67l7yDfIPvxDsNIWWJcRd 8brFYCAOPYE4LpuLGjtSgy370aBe9JmwAm41tE4qF0WhGpcu6TLsKjgMGWa/lHCc JId8+WBfbbQT8XJj/d+3oOETn5/rglvlRhJbnNIwaQpTXxuMC5oz2nGW7rIpIkaA OHo0D20DzGj4nxrQvijZ7DsMkk3F+KJu/4p7M6lpsIPCakknW1WD7IHRfbZ4Oldz 2xH4HfIk7cAdA7i/YUNjlpSgWFQ5OU03J5HAYfC6W37wiGbjdBYf/PKVhJ8hz7+D OCl+yCV00u4fCjlY6zXFea9pGr7Cl1P+sapwKDZ4g+NpNHxBUVY+ahbjQUHYON2W sdzAsLpMMqavCr1o8mcXdm7IPRlLUK9QZUySC9DitPvoF8G2llTAz1mWa4/Oj7/S JMiUERcaL5gdFN8EgEKkamFgLJguYquAjGtiowa51EMbnZG0Q2yWUcrEBFHWBEZT RW1u6r4ChIrPE9X5ljfFpQyKG6jFhYFXG+iVlgTB7F2ZWhjPAXi/tLbBnvIcci1m Md4XFm/bBJj/yNXdPuCi+CtvvdpZ/d4LQn4B7By5bIo1QjCb4Zx5n2Tq5xnYZUOI CnSVnNSkwLbbrAVtYOVWnrSuwR33JQnqeGHdM+XYBBwKBRhrx+ZgFWD7N6Gm95PU xXSxkgYVXI4sgi7Lh3Ia =2Vmc -END PGP SIGNATURE- I have on patch file that Lo sent. Three different files are on it with the assumption that the patch-root is /usr/src. I'm thinking about snipping it twice and then applying each subpatch within the proper subdirectory. Now, this would not when Index:reference is at the header of each, right? One not one in first sentence. Insert hurt between not when in last sentence. I'm doing patch -p *.diff and the process is taking some time. What am I doing wrong? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On Sun, Mar 2, 2014 at 4:04 PM, Joe Nosay superbisq...@gmail.com wrote: On Sun, Mar 2, 2014 at 3:20 PM, Joe Nosay superbisq...@gmail.com wrote: On Sun, Mar 2, 2014 at 3:19 PM, Joe Nosay superbisq...@gmail.com wrote: On Sun, Mar 2, 2014 at 3:08 PM, Xin Li delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 3/2/14, 10:42 AM, Joe Nosay wrote: On Thu, Feb 27, 2014 at 3:22 AM, Joe Nosay superbisq...@gmail.com wrote: On Wed, Feb 26, 2014 at 11:19 PM, Xin Li delp...@delphij.net wrote: On 02/26/14 18:52, Joe Nosay wrote: On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis bro...@freebsd.org wrote: On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks Thanks. I will ask kevlo and maybe bring it up on freebsd-net. It has to do with an implementation of the JACK server using UDP Lite for transferring data. http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html Looks like nobody proposed a patch? I think the concern was that this is not very useful in real-world scenarios due to link layer error detection mechanism but that doesn't raise a red flag to me assuming this is sufficiently self contained feature as it would improve compatibility with other operating systems. Cheers, https://github.com/torelizer/jack_trauma Not my project; but, I want to port it to FreeBSD. First is to get it to build from source. Use your raspberry pi with FreeBSD to broadcast your tunes and all. Thanks for all of the input. The project is being reworked to improve the code. Kevin Lo have a patchset but needs someone to do performance testing (its impact on non-UDPLite applications), test with vimage, etc: http://people.freebsd.org/~kevlo/udplite.diff http://people.freebsd.org/~kevlo/udp-v.diff Are you interested in working on these and report back? Cheers, -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJTE4+mAAoJEJW2GBstM+nsthoQAIW67l7yDfIPvxDsNIWWJcRd 8brFYCAOPYE4LpuLGjtSgy370aBe9JmwAm41tE4qF0WhGpcu6TLsKjgMGWa/lHCc JId8+WBfbbQT8XJj/d+3oOETn5/rglvlRhJbnNIwaQpTXxuMC5oz2nGW7rIpIkaA OHo0D20DzGj4nxrQvijZ7DsMkk3F+KJu/4p7M6lpsIPCakknW1WD7IHRfbZ4Oldz 2xH4HfIk7cAdA7i/YUNjlpSgWFQ5OU03J5HAYfC6W37wiGbjdBYf/PKVhJ8hz7+D OCl+yCV00u4fCjlY6zXFea9pGr7Cl1P+sapwKDZ4g+NpNHxBUVY+ahbjQUHYON2W sdzAsLpMMqavCr1o8mcXdm7IPRlLUK9QZUySC9DitPvoF8G2llTAz1mWa4/Oj7/S JMiUERcaL5gdFN8EgEKkamFgLJguYquAjGtiowa51EMbnZG0Q2yWUcrEBFHWBEZT RW1u6r4ChIrPE9X5ljfFpQyKG6jFhYFXG+iVlgTB7F2ZWhjPAXi/tLbBnvIcci1m Md4XFm/bBJj/yNXdPuCi+CtvvdpZ/d4LQn4B7By5bIo1QjCb4Zx5n2Tq5xnYZUOI CnSVnNSkwLbbrAVtYOVWnrSuwR33JQnqeGHdM+XYBBwKBRhrx+ZgFWD7N6Gm95PU xXSxkgYVXI4sgi7Lh3Ia =2Vmc -END PGP SIGNATURE- I have on patch file that Lo sent. Three different files are on it with the assumption that the patch-root is /usr/src. I'm thinking about snipping it twice and then applying each subpatch within the proper subdirectory. Now, this would not when Index:reference is at the header of each, right? One not one in first sentence. Insert hurt between not when in last sentence. I'm doing patch -p *.diff and the process is taking some time. What am I doing wrong? Syntax. Rebuild reinstall the source portions in common then find an application that uses udplite, right? Du. Thanks. Yuhhh ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On Wed, Feb 26, 2014 at 11:19 PM, Xin Li delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/26/14 18:52, Joe Nosay wrote: On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis bro...@freebsd.org wrote: On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks Thanks. I will ask kevlo and maybe bring it up on freebsd-net. It has to do with an implementation of the JACK server using UDP Lite for transferring data. http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html Looks like nobody proposed a patch? I think the concern was that this is not very useful in real-world scenarios due to link layer error detection mechanism but that doesn't raise a red flag to me assuming this is sufficiently self contained feature as it would improve compatibility with other operating systems. Cheers, - -- Xin LI delp...@delphij.nethttps://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCgAGBQJTDrzbAAoJEJW2GBstM+nsJVoP/29XRcleHMnAVa1UOG0+CD2y 0e/pAmk5vay599gjmiKSAuTSeKNaawRF3FZP+QsxhKw/lNTYEHlppUw7FDc01NqO pk1GsIu+mVuLlzZBNSuAkXdMMzJz5OKfY9GeK7Uw4iumiNP5LKpoC1RaYqLVASGf JH6tqJdSVnD+apWxV/PF4orCXZECFLkQZhbgZe+2nni+te6OfzIbkjhBqn8ZIDNY m9GbYwkTEATBDcMGgl9F0wBfcLhQLF4p4+TnsCguP0HAbxCtbZmt3SXe6Xt4y2YE iHlO/qstGKrl61aiehtpasjiljJaN5ucmuv8XDGbix4cghiJCJAGmxXGxCoHs/Uq vkn88wfV901pjYWPWf9HmTdjSmsck0k2+srWYlJuRymVKvMsL2mwPky+QL9SZ6MY NJ8kXUl5szFwdN4OtO+1iUvVZNLkVDlV5bmnc5KOkciFRoLuTq1/f/xzGj/YDZpx 2DxjddVyvJ6YhrUSSAGoOcdxIpDejKfVif0ANoocsKLAnTHtNxdB76doJH4wBl+W LAl9a9IqVOiefFe9qb6tZky3lft3HUe4XvLJPraKTfbvA9VAKPqZbc2Z8eeoqb49 LPC2n8WnlnaXB9KXKSWTLXbdcY2L+HnAt2+DEv4viSyKSXQg00aEbm+R95h1pTz7 oMv/8VGg5akyRQtkTTIx =ukUF -END PGP SIGNATURE- https://github.com/torelizer/jack_trauma Not my project; but, I want to port it to FreeBSD. First is to get it to build from source. Use your raspberry pi with FreeBSD to broadcast your tunes and all. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
UDP Lite support
The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks pgpRX09Q7lnzF.pgp Description: PGP signature
Re: UDP Lite support
On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis bro...@freebsd.org wrote: On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks Thanks. I will ask kevlo and maybe bring it up on freebsd-net. It has to do with an implementation of the JACK server using UDP Lite for transferring data. http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html That thread. Apologies for any inconvenience, Desmond ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: UDP Lite support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/26/14 18:52, Joe Nosay wrote: On Wed, Feb 26, 2014 at 9:19 PM, Brooks Davis bro...@freebsd.org wrote: On Wed, Feb 26, 2014 at 07:36:29PM -0500, Joe Nosay wrote: The last thread on this was in 2006. Has it ever been reconsidered or is the likelihood of too many damaged packets the reason for not supporting? I'm not sure where to put this question. Apologies for the noise. You've provided next to no context. What is the question? What thread are you referring to? If this is the usual UDP then freebsd-net would be vastly more appropriate than -current. -- Brooks Thanks. I will ask kevlo and maybe bring it up on freebsd-net. It has to do with an implementation of the JACK server using UDP Lite for transferring data. http://freebsd.1045724.n5.nabble.com/UDP-lite-for-FreeBSD-td4010236.html Looks like nobody proposed a patch? I think the concern was that this is not very useful in real-world scenarios due to link layer error detection mechanism but that doesn't raise a red flag to me assuming this is sufficiently self contained feature as it would improve compatibility with other operating systems. Cheers, - -- Xin LI delp...@delphij.nethttps://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCgAGBQJTDrzbAAoJEJW2GBstM+nsJVoP/29XRcleHMnAVa1UOG0+CD2y 0e/pAmk5vay599gjmiKSAuTSeKNaawRF3FZP+QsxhKw/lNTYEHlppUw7FDc01NqO pk1GsIu+mVuLlzZBNSuAkXdMMzJz5OKfY9GeK7Uw4iumiNP5LKpoC1RaYqLVASGf JH6tqJdSVnD+apWxV/PF4orCXZECFLkQZhbgZe+2nni+te6OfzIbkjhBqn8ZIDNY m9GbYwkTEATBDcMGgl9F0wBfcLhQLF4p4+TnsCguP0HAbxCtbZmt3SXe6Xt4y2YE iHlO/qstGKrl61aiehtpasjiljJaN5ucmuv8XDGbix4cghiJCJAGmxXGxCoHs/Uq vkn88wfV901pjYWPWf9HmTdjSmsck0k2+srWYlJuRymVKvMsL2mwPky+QL9SZ6MY NJ8kXUl5szFwdN4OtO+1iUvVZNLkVDlV5bmnc5KOkciFRoLuTq1/f/xzGj/YDZpx 2DxjddVyvJ6YhrUSSAGoOcdxIpDejKfVif0ANoocsKLAnTHtNxdB76doJH4wBl+W LAl9a9IqVOiefFe9qb6tZky3lft3HUe4XvLJPraKTfbvA9VAKPqZbc2Z8eeoqb49 LPC2n8WnlnaXB9KXKSWTLXbdcY2L+HnAt2+DEv4viSyKSXQg00aEbm+R95h1pTz7 oMv/8VGg5akyRQtkTTIx =ukUF -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
