All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Nicolas Pitre <nico@cam.org>
Cc: mfuzzey@gmail.com, netdev@vger.kernel.org
Subject: Re: [RFC PATCH] Ethtool style in kernel network driver configuration.
Date: Thu, 11 Jun 2009 20:31:59 +0100	[thread overview]
Message-ID: <1244748719.2785.72.camel@achroite> (raw)
In-Reply-To: <alpine.LFD.2.00.0906111452340.31536@xanadu.home>

On Thu, 2009-06-11 at 15:08 -0400, Nicolas Pitre wrote:
[...]
> > Please note, I'm talking about an init script -
> > which you surely must have - not an initramfs, which I recognise is
> > optional and unnecessary for most embedded systems.
> 
> An init script is already a luxury for some systems.

And so is an Ethernet port.  Instead of talking about hypotheticals, why
not talk about the system you need this workaround for?

> It means a 
> script, which implies a shell, and of course the tool binaries (ethtool 
> in this case) to be called by your shell.  Not only those do bloat your 
> system (the shell + tool + script occupies way more space than the 
> proposed module)

Well, if you're replacing init - which is generally a really bad idea,
by the way - you can build the ethtool API calls in there along with all
your other application-specific stuff.  The ethtool API isn't terribly
complex.

> and then you do have to maintain those components as 
> well, but it also has impact on boot time.  Remember that we're not 
> talking about systems bragging about their boot time being under 20 
> seconds here, but systems that need to be operational in only a couple 
> miliseconds.

If you want to boot that quickly you definitely don't want to have to
wait for PHY operations.

> > I was thinking that you could add it to the platform data for such
> > devices, not that you would put board-specific quirks in the drivers.
> 
> And what if the majority of users for a driver simply don't need such a 
> thing?  And how do you do that if the driver you need is for a PCI 
> device?

Any device can have platform data; it's part of struct device.

> And why would driver specific kirks be better than a generic 
> module that can handle those params in a uniform way across all drivers?  
> Especially if you can ignore said module if you don't need/want to use 
> it?

Because its raison d'etre is apparently to disable the broken link
modes, and it doesn't do that properly.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.


  reply	other threads:[~2009-06-11 19:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 17:34 [RFC PATCH] Ethtool style in kernel network driver configuration Martin Fuzzey
2009-06-10 18:02 ` Joe Perches
2009-06-11  2:02 ` Ben Hutchings
2009-06-11  3:55   ` Nicolas Pitre
2009-06-11  6:47   ` Martin Fuzzey
2009-06-11 14:54     ` Ben Hutchings
2009-06-11 16:22       ` Nicolas Pitre
2009-06-11 16:52         ` Ben Hutchings
2009-06-11 17:44           ` Nicolas Pitre
2009-06-11 18:29             ` Ben Hutchings
2009-06-11 19:08               ` Nicolas Pitre
2009-06-11 19:31                 ` Ben Hutchings [this message]
2009-06-11 20:24                   ` Nicolas Pitre
2009-06-11 20:48                     ` Ben Hutchings
2009-06-11 21:39                       ` Martin Fuzzey
2009-06-12  0:15                     ` David Miller
2009-06-12  0:38                       ` Nicolas Pitre
2009-06-12  2:57                         ` David Miller
2009-06-11 17:45           ` Martin Fuzzey
2009-06-12  0:09             ` David Miller
2009-06-12 10:50               ` Mark Brown
2009-06-12 11:33                 ` David Miller
2009-06-12 12:24                   ` Mark Brown
2009-06-13  0:01                     ` David Miller
2009-06-13 17:10                       ` Mark Brown
2009-06-12 12:19               ` Martin Fuzzey
2009-06-13  0:01                 ` David Miller
2009-06-13  7:00                   ` Martin Fuzzey
2009-06-13  7:07                     ` David Miller
2009-06-13  7:51                       ` Martin Fuzzey
2009-06-13  8:07                         ` David Miller
2009-06-13  9:29                           ` Martin Fuzzey
2009-06-14 18:39                       ` Martin Fuzzey
2009-06-12  0:07           ` David Miller
2009-06-12  0:03         ` 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=1244748719.2785.72.camel@achroite \
    --to=bhutchings@solarflare.com \
    --cc=mfuzzey@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nico@cam.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.