From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: "Bernard, f6bvp" <f6bvp@free.fr>
Cc: linux-hams@vger.kernel.org
Subject: Re: [PATCH 0/7] ROSE: Misc fixes
Date: Fri, 22 Jul 2011 11:56:41 +0100 [thread overview]
Message-ID: <20110722105641.GA24477@linux-mips.org> (raw)
In-Reply-To: <4E293E96.3030708@free.fr>
On Fri, Jul 22, 2011 at 11:10:46AM +0200, Bernard, f6bvp wrote:
> Replacement patch applied and install went fine.
> Nearly 24 hours after running the new "atomic" rose code
> on two systems, I observe that 'use' parameter is 0, something I
> never observed before. It used to be positive on some link and
> rarely
> displaying a high number meaning underflow negative values.
>
> >/proc/net/rose_neigh
> >addr callsign dev count use mode restart t0 tf digipeaters
> >00020 F6BVP-5 ax0 1 0 DTE no 0 0
> >00019 F6BVP-7 ax0 2 0 DTE no 0 0
> >00018 F6BVP-9 ax2 2 0 DTE no 0 0
> >00017 F3KT-11 ax0 3 0 DTE yes 0 0
> >00016 F8COJ-11 ax0 2 0 DCE yes 0 0
> >00015 F6GGY-9 ax0 3 0 DTE no 0 0
> >00014 F4BWT-11 ax0 4 0 DTE no 0 0
> >00013 F1MVP-5 ax0 2 0 DTE no 0 0
> >00012 F5KBW-9 ax0 6 0 DTE no 0 0
> >00011 IR5AG-13 ax0 2 0 DTE no 0 0
> >00010 K4GBB-9 ax0 4 0 DCE yes 0 0
> >00009 KD4YAL-9 ax0 2 0 DTE no 0 0
> >00008 KP4DJT-9 ax0 3 0 DTE yes 0 0
> >00007 P43L-4 ax0 5 0 DCE yes 0 0
> >00006 VK2XB-2 ax0 2 0 DTE no 0 0
> >00005 VK2TV-2 ax0 2 0 DTE no 0 0
> >00004 VK7HDM-5 ax0 2 0 DTE no 0 0
> >00003 YN1BBS-9 ax0 5 0 DTE no 0 0
> >00002 TI2HAS-9 ax0 5 0 DTE no 0 0
> >00001 RSLOOP-0 ??? 1 2 DCE yes 0 0
>
> I guess this is a pretty good thing.
>
> I will try removing rose module and report if any progress
> on that point too.
Most excellent! Take your time for testing - unfortunately we missed
the v3.0 train already but it would be great if we could backport these
fixes to -stable after some more positive testing.
Is the system that was having these issues btw. running a preemptable kernel
or does it have multiple cores or hyperthreading?
Thanks,
Ralf
next prev parent reply other threads:[~2011-07-22 10:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 9:00 [PATCH 0/7] ROSE: Misc fixes Ralf Baechle
2011-07-20 0:21 ` [PATCH 1/7] NET: ROSE: Fix race in SIOCRSSL2CALL ioctl accessing userspace Ralf Baechle
2011-07-20 0:21 ` [PATCH 2/7] NET: ROSE: Factor our common code from functions Ralf Baechle
2011-07-20 0:37 ` [PATCH 3/7] NET: ROSE: Protect rose_callsign with a spinlock Ralf Baechle
2013-08-06 17:57 ` [PATCH] ax25tools mheard : don't display empty records f6bvp@free
2013-08-07 8:17 ` Thomas Osterried
2013-08-07 10:06 ` f6bvp@free
2013-08-09 8:10 ` Thomas Osterried
2011-07-20 8:11 ` [PATCH 4/7] NET: ROSE: Make neighbour->use atomic Ralf Baechle
2011-07-20 8:11 ` [PATCH 5/7] NET: ROSE: Make rose_neigh_no atomic Ralf Baechle
2011-07-20 18:09 ` [PATCH v2 " Ralf Baechle
2011-07-20 8:11 ` [PATCH 6/7] NET: ROSE: Move return statements hidden behind an if to their own line Ralf Baechle
2011-07-20 8:11 ` [PATCH 7/7] NET: ROSE: Fix formatting Ralf Baechle
2011-07-20 17:15 ` [PATCH 0/7] ROSE: Misc fixes Bernard, f6bvp
2011-07-20 17:59 ` Ralf Baechle DL5RB
2011-07-22 9:10 ` Bernard, f6bvp
2011-07-22 10:56 ` Ralf Baechle DL5RB [this message]
2011-07-22 16:12 ` f6bvp
2011-07-23 13:28 ` Ralf Baechle DL5RB
2011-07-29 22:32 ` f6bvp
2011-08-08 13:40 ` f6bvp
2011-08-08 14:06 ` Ralf Baechle
2011-08-08 15:33 ` f6bvp
2011-08-19 13:07 ` f6bvp
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=20110722105641.GA24477@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=f6bvp@free.fr \
--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