linux-hams.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ranch <linux-hams@trinnet.net>
To: linux-hams@vger.kernel.org
Subject: Re: kernel ax25: lost and out-of-order data
Date: Sat, 13 Feb 2016 14:23:56 -0800	[thread overview]
Message-ID: <56BFACFC.70107@trinnet.net> (raw)
In-Reply-To: <20160213124103.GE24276@x-berg.in-berlin.de>


Hello Thomas,

> 1. New findings:
>    if the kernel runs on a single CPU machine, everything is ok. I transferred the 2MB testfile three times and it has been always received ok.
>    => I suppose it's an SMP issue.

Wow.. that's a key find!  Nice work!  Now that you narrowed this down to 
a threading issue with a easy way to reproduce it, I hope you'll get 
some traction here from the local kernel experts.  If you don't see much 
movement, I imagine taking this up to the main kernel list would be 
warranted.

--David
KI6ZHD


      reply	other threads:[~2016-02-13 22:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 18:12 kernel ax25: lost and out-of-order data Thomas Osterried
2016-02-13 12:41 ` Thomas Osterried
2016-02-13 22:23   ` David Ranch [this message]

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=56BFACFC.70107@trinnet.net \
    --to=linux-hams@trinnet.net \
    --cc=linux-hams@vger.kernel.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).