Hi Ingo,
Thanks for your effort in unicode support. I hope my feedback as a
native Persian would be helpful.
Ingo Schwarze wrote:
> If i understand correctly, xterm(1) does indeed have that problem.
> I prepared a test file that contains, in this order,
>
> - some Latin characters
> - the Ar
On 09/09/19(Mon) 16:37, Stefan Sperling wrote:
> On Mon, Sep 09, 2019 at 03:10:04PM +0200, Stefan Sperling wrote:
> > The wifi stack currently calls if_input once per packet instead of once
> > per interrupt. To make the wifi layer play nicely with the network stack
> > we can split ieee80211_input
Hi Stefan,
* Stefan Sperling wrote:
> On Mon, Sep 09, 2019 at 03:10:04PM +0200, Stefan Sperling wrote:
> > The wifi stack currently calls if_input once per packet instead of once
> > per interrupt. To make the wifi layer play nicely with the network stack
> > we can split ieee80211_input() into tw
> Date: Mon, 9 Sep 2019 13:29:32 +0200
> From: Alexander Bluhm
>
> On Sat, Sep 07, 2019 at 04:07:22PM +0200, Mark Kettenis wrote:
> > The diff below should fix one of the issues uncovered by the
> > acpipci(4) changes that I just backed out.
> >
> > On some systems, ACPI specifies overlapping reg
On Mon 09/09/2019 16:37, Stefan Sperling wrote:
> On Mon, Sep 09, 2019 at 03:10:04PM +0200, Stefan Sperling wrote:
> > The wifi stack currently calls if_input once per packet instead of once
> > per interrupt. To make the wifi layer play nicely with the network stack
> > we can split ieee80211_inpu
this seems to work fine on
iwm0 at pci2 dev 0 function 0 "Intel Dual Band Wireless AC 7260" rev 0x83, msi
download is considerably less wobbly, upload also benefits a bit(?):
before:
[florian@x1:~]$ tcpbench -t 10 192.168.178.73
elapsed_ms bytes mbps bwidth
1001
On Mon, Sep 09, 2019 at 03:10:04PM +0200, Stefan Sperling wrote:
> The wifi stack currently calls if_input once per packet instead of once
> per interrupt. To make the wifi layer play nicely with the network stack
> we can split ieee80211_input() into two parts:
Updated diff which avoids purging t
robert@ noticed that iwm(4) Rx throughput increased after running:
sysctl net.link.ifrxq.pressure_drop=32
The default value for this sysctl is 8.
dlg@ explained the problem to me:
[[[
the pressure stuff counts the number of times ifiq_input (which is
called from if_input) gets called befor
On Sat, Sep 07, 2019 at 04:07:22PM +0200, Mark Kettenis wrote:
> The diff below should fix one of the issues uncovered by the
> acpipci(4) changes that I just backed out.
>
> On some systems, ACPI specifies overlapping regions of address space
> that gets forwarded to the PCI bus. Since we use ext
In trying to figure out why since upgrading to 6.5 ports/ntp was
spamming the logs with "adj_systime: Invalid argument" every 20 seconds
on some machines, I found this happened when it was calling adjtime(2)
with a small negative value in tv_usec.
The man page talks about negative deltas, but
I would like to move forward with this.
Is anyone willing to look at this?
On 9/2/19 9:06 AM, Martijn van Duren wrote:
> Hello tech@,
>
> I've worked hard to get SNMPv3 support for snmp(1). Here's the end
> result. This mail contains the full diff for people just wanting to
> test, the follow up
11 matches
Mail list logo
