All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: Marco Varlese <marco.varlese@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Port attributes configuration
Date: Tue, 29 Jul 2014 06:46:37 -0700	[thread overview]
Message-ID: <53D7A5BD.1070805@gmail.com> (raw)
In-Reply-To: <CACWm-Bc4=4We1AfnZpL7O5VkUSKjKBZ-NK6edXW2fE5b_u-e7g@mail.gmail.com>

On 07/29/2014 02:15 AM, Marco Varlese wrote:
> I'm working on a new platform and the network interfaces will have
> quite few new options (roughly 50) to configure. What I definitely
> want to achieve is to use the common tools available on Linux to let
> users configure the port attributes from user-space without writing a
> brand new ad-hoc tool.

Its hard to say without knowing what the attributes are and how many
of them are new.

>
> Considered my requirements I think I've a choice of configuring these
> port attributes via:
> 1) ethtool: this I guess will require patches to the tool itself plus
> patches to the kernel to extend the IOCTL calls performed by it;

Many devices already expose many statistics via ethtool -S and features
via ethtool -k. Depending on the attribute it may make sense to add
it here.

> 2) sysfs: adding new files under /sys/class/net/DEVICE/ and handle the
> sysfs extensions in my kernel driver;

Typically most these are read only options. Without knowing your options
I would guess this is the least likely.

> 3) netlink: I understand this seems to be the path most people prefer
> but I think it will require a new tool to be written?
>

Writing a new tool is not necessarily a bad thing IMO but again need
more details what type of options.

> What would you suggest as the best approach here to have a good
> solution accepted by most?

more details.

>
>
> Thanks,
> Marco
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


-- 
John Fastabend         Intel Corporation

  reply	other threads:[~2014-07-29 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29  9:15 Port attributes configuration Marco Varlese
2014-07-29 13:46 ` John Fastabend [this message]
2014-07-29 17:53 ` Cong Wang

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=53D7A5BD.1070805@gmail.com \
    --to=john.fastabend@gmail.com \
    --cc=marco.varlese@gmail.com \
    --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.