Re: writev() to /dev/bpf from different sockets block

To: tech-net%netbsd.org@localhost
Subject: Re: writev() to /dev/bpf from different sockets block
From: Mouse <mouse%Rodents-Montreal.ORG@localhost>
Date: Sat, 25 Jan 2025 15:04:37 -0500 (EST)

I mostly don't have anything to say on this thread.  But...

> [...]
>      if (errno == ENOBUFS) {
>        delay(750000);
> [...]

> Secondary problem: I couldn't find an effective way to handle
> ENOBUFS, other than with a 750us delay

That looks to me like 750ms, not 750us.  At least, on 9.1 delay() is
documented as taking us, not ns.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse%rodents-montreal.org@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

Follow-Ups:
- Re: writev() to /dev/bpf from different sockets block
  - From: Jason Curl

References:
- writev() to /dev/bpf from different sockets block
  - From: Jason Curl

Prev by Date: writev() to /dev/bpf from different sockets block
Next by Date: Re: writev() to /dev/bpf from different sockets block
Previous by Thread: writev() to /dev/bpf from different sockets block
Next by Thread: Re: writev() to /dev/bpf from different sockets block
Indexes:

Home | Main Index | Thread Index | Old Index