netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mpm@selenic.com
Cc: akpm@linux-foundation.org, jeff@garzik.org,
	netdev@vger.kernel.org, thomas.petazzoni@free-electrons.com
Subject: Re: [patch 12/12] Configure out ethtool support
Date: Wed, 30 Jul 2008 16:21:53 -0700 (PDT)	[thread overview]
Message-ID: <20080730.162153.124485443.davem@davemloft.net> (raw)
In-Reply-To: <1217459102.18911.182.camel@calx>

From: Matt Mackall <mpm@selenic.com>
Date: Wed, 30 Jul 2008 18:05:02 -0500

> On Wed, 2008-07-30 at 15:37 -0700, David Miller wrote:
> > From: Matt Mackall <mpm@selenic.com>
> > Date: Wed, 30 Jul 2008 17:24:26 -0500
> > 
> > > 
> > > On Wed, 2008-07-30 at 14:35 -0700, David Miller wrote:
> > > > This change means you can't configure nearly all of the features on
> > > > your ethernet card.  You can't even configure the link parameters
> > > > without ethtool support.
> > > 
> > > Which is big fat don't-care for the vast majority of users. Various
> > > popular distros don't even install the tool by default.
> > 
> > Are you even aware that the ethtool layer gets invoked by simply
> > enabling IP forwarding or bridgining, in order to disable LRO
> > offloading which conflicts with such uses?
> 
> Oh noes. How ever will my poor webcam get on the internets without that.

Have any firewall rules implemented on that webcam?

It's only a matter of time before other core facilities need
to use ethtool to adjust the device's settings in one way or
another.

So what I said is anything but hyperbole.

  reply	other threads:[~2008-07-30 23:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 19:39 [patch 12/12] Configure out ethtool support akpm
2008-07-30 20:37 ` Stephen Hemminger
2008-07-30 20:48   ` Thomas Petazzoni
2008-07-30 21:01     ` Stephen Hemminger
2008-07-30 21:35       ` Thomas Petazzoni
2008-07-30 21:48         ` Andrew Morton
2008-07-30 21:52           ` Thomas Petazzoni
2008-07-30 22:04             ` Andrew Morton
2008-07-30 23:35               ` Roland Dreier
2008-07-30 21:57           ` David Miller
2008-07-30 22:13             ` Andrew Morton
2008-07-30 22:33               ` David Miller
2008-07-31 10:39               ` David Woodhouse
2008-07-31 10:43                 ` David Miller
2008-07-31 10:49                   ` David Woodhouse
2008-07-31 10:47                 ` David Miller
2008-07-31 15:36                   ` Matt Mackall
2008-07-31 15:59                     ` Stephen Hemminger
2008-07-31 16:11                       ` Matt Mackall
2008-07-31 18:17                     ` Evgeniy Polyakov
2008-07-30 21:35 ` David Miller
2008-07-30 21:44   ` Andrew Morton
2008-07-30 22:24   ` Matt Mackall
2008-07-30 22:37     ` David Miller
2008-07-30 23:05       ` Matt Mackall
2008-07-30 23:21         ` David Miller [this message]
2008-07-31  1:10           ` Matt Mackall
2008-07-31  1:23             ` David Miller
2008-07-31 10:22               ` Kalle Valo

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=20080730.162153.124485443.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=mpm@selenic.com \
    --cc=netdev@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.com \
    /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).