On Wed, Feb 27, 2019 at 12:06:32PM +0100, Solene Rapenne wrote:
> Copy a file over NFS (3 times)
>
> Before patch: 20.51 / 19.74 / 19.74 seconds
> After patch: 14.48 / 15.03 / 14.49 seconds
>
> It gets 25% faster!
Nice :)
> Ping -c100 -i0.2 on local network
>
> Before patch:
On Tue, Feb 26, 2019 at 03:33:23PM +0100, Stefan Sperling wrote:
> On Tue, Feb 26, 2019 at 03:04:35PM +0100, Stefan Sperling wrote:
> > This diff makes the RTS threshold dynamic in 11n mode.
> > I am looking for tests with iwn(4), iwm(4), and athn(4) drivers.
> >
&
On Tue, Feb 26, 2019 at 03:04:35PM +0100, Stefan Sperling wrote:
> This diff makes the RTS threshold dynamic in 11n mode.
> I am looking for tests with iwn(4), iwm(4), and athn(4) drivers.
>
> When there's a lot of competition for air time, RTS can do more harm than
> good be
This diff makes the RTS threshold dynamic in 11n mode.
I am looking for tests with iwn(4), iwm(4), and athn(4) drivers.
When there's a lot of competition for air time, RTS can do more harm than
good because we end up causing more RTS/CTS frames on the air than actual
data frames. So a fixed RTS
On Sat, Mar 11, 2017 at 08:55:54AM +0900, Stefan Sperling wrote:
> On Sat, Mar 04, 2017 at 10:04:51PM +0100, Stefan Sperling wrote:
> > This diff makes the RTS threshold dynamic in 11n mode.
> > It flips the RTS threshold between DEFAULT (512 bytes) and MAX (the
> >
On Sat, Mar 04, 2017 at 10:04:51PM +0100, Stefan Sperling wrote:
> This diff makes the RTS threshold dynamic in 11n mode.
> It flips the RTS threshold between DEFAULT (512 bytes) and MAX (the
> maximum size of a non-aggregated 802.11 frame).
Things have been working fine for me with
