netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, shemminger@linux-foundation.org,
	johannes@sipsolutions.net
Subject: Re: [PATCH] net: Add DEVTYPE support for Ethernet based devices
Date: Sat, 05 Sep 2009 07:52:20 +0200	[thread overview]
Message-ID: <1252129940.27694.9.camel@violet> (raw)
In-Reply-To: <20090904.214615.198838334.davem@davemloft.net>

Hi David,

> > What is ugly about it. Do you have any other recommendation on how let
> > userspace know what type of Ethernet device it is?
> 
> Well, for one thing, you're wasting 48 bytes on 64-bit when all you're
> really intrested in is one string.

the integration with struct device has plenty of other advantages. You
could use all the sysfs magic from it. For example in the next step the
hacking of some sysfs directories can be moved into the subsystem itself
and could be moved out of the core. Wireless would be one of them were
we would benefit here.

> Also, you didn't setup an assignment for plain ethernet devices,
> you just handle the non-traditional devices that do ethernet
> framing.  Is this intentional?

For now it is. Mainly since some non plain Ethernet devices are using
alloc_etherdev instead of just alloc_netdev. So I would have to do some
extra work. I have planned it, but not gotten around it yet.

Regards

Marcel



  reply	other threads:[~2009-09-05  5:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01  7:08 [PATCH] net: Add DEVTYPE support for Ethernet based devices Marcel Holtmann
2009-09-01  7:25 ` Johannes Berg
2009-09-01  7:33   ` Marcel Holtmann
2009-09-05  0:17 ` Marcel Holtmann
2009-09-05  3:27   ` David Miller
2009-09-05  4:34     ` Marcel Holtmann
2009-09-05  4:46       ` David Miller
2009-09-05  5:52         ` Marcel Holtmann [this message]
2009-09-05  5:55           ` David Miller
2009-09-05  4:49 ` Stephen Hemminger
2009-09-05  5:55   ` Marcel Holtmann
2009-09-11 19:37 ` 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=1252129940.27694.9.camel@violet \
    --to=marcel@holtmann.org \
    --cc=davem@davemloft.net \
    --cc=johannes@sipsolutions.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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).