All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: <netdev@vger.kernel.org>
Subject: Re: ppp, "Features changed" flooding the log
Date: Fri, 20 May 2011 16:44:23 +0300	[thread overview]
Message-ID: <e04d91916983d0a9274087cd2f5ef64d@visp.net.lb> (raw)
In-Reply-To: <a08c037f093701d9a2d187d04ac85fee@visp.net.lb>

 On Fri, 20 May 2011 16:42:08 +0300, Denys Fedoryshchenko wrote:
> Hi
>
> Is it supposed to be like this?
> [   41.575487] ppp313: Features changed: 0x00006800 -> 0x00006000
> [   41.681499] ppp314: Features changed: 0x00006800 -> 0x00006000
> [   41.796728] ppp315: Features changed: 0x00006800 -> 0x00006000
> [   41.909575] ppp316: Features changed: 0x00006800 -> 0x00006000
> [   42.027802] ppp317: Features changed: 0x00006800 -> 0x00006000
> [   42.142698] ppp318: Features changed: 0x00006800 -> 0x00006000
> [   42.292753] ppp319: Features changed: 0x00006800 -> 0x00006000
> [   42.408706] ppp320: Features changed: 0x00006800 -> 0x00006000
> [   42.544745] ppp321: Features changed: 0x00006800 -> 0x00006000
> [   42.634743] ppp322: Features changed: 0x00006800 -> 0x00006000
> [   42.740747] ppp323: Features changed: 0x00006800 -> 0x00006000
> [   42.856579] ppp324: Features changed: 0x00006800 -> 0x00006000
>
> I guess ppp dropping GSO, but is it should be there on first place?
> GSO is disabled on all ethernet interfaces.
 And as i see GRO enabled there, i guess it can be harmful for shapers, 
 how to disable it?
 NewNet-PPPoE ~ # ethtool -K ppp0 gro off
 Cannot set device GRO settings: Operation not supported
 Or there is no need for that?

  reply	other threads:[~2011-05-20 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20 13:42 ppp, "Features changed" flooding the log Denys Fedoryshchenko
2011-05-20 13:44 ` Denys Fedoryshchenko [this message]
2011-05-20 14:00   ` Eric Dumazet
2011-05-20 18:22 ` David Miller

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=e04d91916983d0a9274087cd2f5ef64d@visp.net.lb \
    --to=denys@visp.net.lb \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.