b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Enable LockLess TX for softif
Date: Tue, 11 Sep 2018 18:07:18 +0200	[thread overview]
Message-ID: <12395173.KTiadihbU5@bentobox> (raw)
In-Reply-To: <20180911155942.15494-1-sven@narfation.org>

[-- Attachment #1: Type: text/plain, Size: 182 bytes --]

On Dienstag, 11. September 2018 17:59:42 CEST Sven Eckelmann wrote:
[...]
> * without LLX: 349 Mibit/s
> * with LLX:    563 Mibit/s

I know, it is called LLTX :(

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-09-11 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 15:59 [B.A.T.M.A.N.] [PATCH] batman-adv: Enable LockLess TX for softif Sven Eckelmann
2018-09-11 16:07 ` Sven Eckelmann [this message]
2018-09-14 17:48 ` Sven Eckelmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=12395173.KTiadihbU5@bentobox \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).