search for: ms_timer

Signed-off-by: Julien Viard de Galbert <jviarddegalbert at online.net> --- efi/udp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/efi/udp.c b/efi/udp.c index 1088f47..b0f13ad 100644 --- a/efi/udp.c +++ b/efi/udp.c @@ -163,7 +163,7 @@ void core_udp_connect(struct pxe_pvt_inode *socket, uint32_t ip, } else { udata.UseDefaultAddress = FALSE;

...recursion limit and retry the same servers several times as the UDP > packets may get lost. And coding style improvement. As you noted, you don't accommodate timeouts which is probably the most critical operation this doesn't have. We can't stay in the query forever. jiffies() and ms_timer() are the two available in the core. core/legacynet/dnsresolv.c used jiffies() but ms_timer() should be dealing with millisecond values, not 55ms jiffies and about CLK_TCK jiffies per second. An alternative way to just stub it is to merge everything but the actual call that starts sending UDP pack...

...al times as the UDP > >> packets may get lost. And coding style improvement. > > > > As you noted, you don't accommodate timeouts which is probably the > > most critical operation this doesn't have. We can't stay in the query > > forever. jiffies() and ms_timer() are the two available in the core. > > core/legacynet/dnsresolv.c used jiffies() but ms_timer() should be > > dealing with millisecond values, not 55ms jiffies and about CLK_TCK > > jiffies per second. > > Not sure I understand everything correctly. > Currently, the co...

...ry the same servers several times as the UDP >> packets may get lost. And coding style improvement. > > As you noted, you don't accommodate timeouts which is probably the > most critical operation this doesn't have. We can't stay in the query > forever. jiffies() and ms_timer() are the two available in the core. > core/legacynet/dnsresolv.c used jiffies() but ms_timer() should be > dealing with millisecond values, not 55ms jiffies and about CLK_TCK > jiffies per second. Not sure I understand everything correctly. Currently, the code won't stay in the query...

On Tue, Sep 15, 2015 at 05:22:40AM -0400, Gene Cumm via Syslinux wrote: > On Sep 10, 2015 1:32 AM, "celelibi--- via Syslinux" <syslinux at zytor.com> wrote: > > > > From: Sylvain Gault <sylvain.gault at gmail.com> > > > > Despite having native network capabilities, UEFI 2.4 (the most > > widely deployed at the moment) has no native DNS

...e the BIOS_timer at 0x046C but it has problems emulating a "real" timer interrupt to be hooked... That's the real problem. Just testing I have replaced the timing functions #define BIOS_timer 0x046C // Timer ticks typedef uint32_t jiffies_t; extern volatile jiffies_t __jiffies, __ms_timer; static inline jiffies_t jiffies(void) { return (*(volatile uint32_t *)BIOS_timer); } typedef uint32_t mstime_t; typedef int32_t mstimediff_t; static inline mstime_t ms_timer(void) { return ((*(volatile uint32_t *)BIOS_timer) * 55); } lpxelinux.0 hangs while legacy works OK. I think we should...

On 03/01/16 21:11, H. Peter Anvin via Syslinux wrote: > On 03/01/16 07:21, Patrick Masotta via Syslinux wrote: >> >> At the moment I'm seeing timing issues on TFTP transfers (lwIP depends >> on the new interrupt based timer). I have consistently detected >> >> multiple Requests, double ACKs, etc. All these problems seem to be >> >> sourced on the