Comments

• 

  over 6 years ago by mkubecek | Reply

  I played a bit already, here is a small demo.

×
Edit Comment 2684
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
I played a bit already, here is [a small demo](http://paste.opensuse.org/view/simple/25168092).
 
×
Reply to mkubecek
I played a bit already, here is a small demo.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  over 6 years ago by mkubecek | Reply

  End-of-hackweek status: disappointing, to be honest. Because of a series of P0/P1 bugs, not much time was left to work on the project. The plan was to have 8-10 most common subcommands implemented on both kernel and ethtool side, ready for an RFC submission, and maybe also some work on wireshark dissector. Reality is much less impressive:

  • kernel: basic infrastructure, GET_DRVINFO, GET_SETTINGS and half of SET_SETTINGS
  • ethtool: basic infrastructure, ethtool -i <dev>

  Current code can be found in mkubece/ethnl on Github and home:mkubecek:ethnl OBS project. Let's hope we can get to an RFC submission by the end of this week (I would like to have ethtool ( | -s | -i ) <dev> working on both sides for that).

×
Edit Comment 3030
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
End-of-hackweek status: disappointing, to be honest. Because of a series of P0/P1 bugs, not much time was left to work on the project. The plan was to have 8-10 most common subcommands implemented on both kernel and ethtool side, ready for an RFC submission, and maybe also some work on wireshark dissector. Reality is much less impressive: * kernel: basic infrastructure, `GET_DRVINFO`, `GET_SETTINGS` and half of `SET_SETTINGS` * ethtool: basic infrastructure, `ethtool -i <dev>` Current code can be found in [mkubece/ethnl on Github](https://github.com/mkubecek/ethnl) and [home:mkubecek:ethnl OBS project](https://build.opensuse.org/project/show/home:mkubecek:ethnl). Let's hope we can get to an RFC submission by the end of this week (I would like to have `ethtool ( | -s | -i ) <dev>` working on both sides for that).
 
×
Reply to mkubecek
End-of-hackweek status: disappointing, to be honest. Because of a series of P0/P1 bugs, not much time was left to work on the project. The plan was to have 8-10 most common subcommands implemented on both kernel and ethtool side, ready for an RFC submission, and maybe also some work on wireshark dissector. Reality is much less impressive:
• kernel: basic infrastructure, GET_DRVINFO, GET_SETTINGS and half of SET_SETTINGS
• ethtool: basic infrastructure, ethtool -i <dev>
Current code can be found in mkubece/ethnl on Github and home:mkubecek:ethnl OBS project. Let's hope we can get to an RFC submission by the end of this week (I would like to have ethtool ( | -s | -i ) <dev> working on both sides for that).
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  almost 6 years ago by mkubecek | Reply

  Marked the project for Hackweek 17 but I won't actually have Hackweek 17 in the usual sense due to Netdev conference. Instead, the plan is to dedicate five days (probably five Fridays in near future) to the project.

  Current state: kernel supports GET_DRVINFO, {G,S}ET_SETTINGS and {G,S}ET_PARAMS, dumps for all supported requests and notifications for SETTINGS and PARAMS (DRVINFO is read only by nature so there shouldn't be anything to notify). All of these requests are also supported by ethtool; the code for dumps (use* as device name) and monitoring (use --monitor as first parameter) also exists but the parser needs a bit more work to be presentable.

×
Edit Comment 3512
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Marked the project for Hackweek 17 but I won't actually have Hackweek 17 in the usual sense due to Netdev conference. Instead, the plan is to dedicate five days (probably five Fridays in near future) to the project. Current state: kernel supports `GET_DRVINFO`, `{G,S}ET_SETTINGS` and `{G,S}ET_PARAMS`, dumps for all supported requests and notifications for `SETTINGS` and `PARAMS` (`DRVINFO` is read only by nature so there shouldn't be anything to notify). All of these requests are also supported by ethtool; the code for dumps (use`*` as device name) and monitoring (use `--monitor` as first parameter) also exists but the parser needs a bit more work to be presentable.
 
×
Reply to mkubecek
Marked the project for Hackweek 17 but I won't actually have Hackweek 17 in the usual sense due to Netdev conference. Instead, the plan is to dedicate five days (probably five Fridays in near future) to the project.
Current state: kernel supports GET_DRVINFO, {G,S}ET_SETTINGS and {G,S}ET_PARAMS, dumps for all supported requests and notifications for SETTINGS and PARAMS (DRVINFO is read only by nature so there shouldn't be anything to notify). All of these requests are also supported by ethtool; the code for dumps (use* as device name) and monitoring (use --monitor as first parameter) also exists but the parser needs a bit more work to be presentable.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  almost 5 years ago by mkubecek | Reply

  Status update just before Hackweek 18.

  Kernel series is almost ready for upstream submission of first part. The main missing part is unified request header and unified processing of it. There may also be some minor issues found in v5 review. Submitting v6 is the primary goal for Hackween 18 but it should only take part of the week (the smaller the better).

  More work needs to be done on userspace ethtool utility which is lagging behind a bit:

  • without EVENT notifications (rejected by upstream), monitor will need "lazy load" of string sets
  • some commands will require rtnetlink or devlink; rethink the context structure and socket handling
  • monitor needs to also listen to and react to rtnetlink and devlink notifications
  • syntax extensions need to be documented in man page
  • new debugging options showing structure of sent/received messages
  • use the same parser to interpret bad attribute offset from extack error/warning messages

×
Edit Comment 3842
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
#### Status update just before Hackweek 18. Kernel series is almost ready for upstream submission of first part. The main missing part is unified request header and unified processing of it. There may also be some minor issues found in v5 review. Submitting v6 is the primary goal for Hackween 18 but it should only take part of the week (the smaller the better). More work needs to be done on userspace ethtool utility which is lagging behind a bit: * without `EVENT` notifications (rejected by upstream), monitor will need "lazy load" of string sets * some commands will require rtnetlink or devlink; rethink the context structure and socket handling * monitor needs to also listen to and react to rtnetlink and devlink notifications * syntax extensions need to be documented in man page * new debugging options showing structure of sent/received messages * use the same parser to interpret bad attribute offset from extack error/warning messages
 
×
Reply to mkubecek
Status update just before Hackweek 18.
Kernel series is almost ready for upstream submission of first part. The main missing part is unified request header and unified processing of it. There may also be some minor issues found in v5 review. Submitting v6 is the primary goal for Hackween 18 but it should only take part of the week (the smaller the better).
More work needs to be done on userspace ethtool utility which is lagging behind a bit:
• without EVENT notifications (rejected by upstream), monitor will need "lazy load" of string sets
• some commands will require rtnetlink or devlink; rethink the context structure and socket handling
• monitor needs to also listen to and react to rtnetlink and devlink notifications
• syntax extensions need to be documented in man page
• new debugging options showing structure of sent/received messages
• use the same parser to interpret bad attribute offset from extack error/warning messages
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  about 4 years ago by mkubecek | Reply

  Status update before Hackweek 19

  After few more review rounds and rewrites, initial part of the kernel series was accepted to net-next tree and reached mainline as part of the 5.6 merge window (so that it's going to appear in v5.6-rc1. What is in mainline at the moment allows netlink based implementation of

  • ethtool <dev>
  • ethtool s <dev> ...
  • ethtool -P <dev> (using rtnetlink)

  and corresponding notifications.

  The userspace ethtool counterpart, however, will need a lot of work to make it ready for upstream submission. As it is highly desirable to have it in ethtool 5.6 release, this is going to be the primary focus at least for the first part of Hackweek 19.

×
Edit Comment 4344
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
### Status update before Hackweek 19 After few more review rounds and rewrites, initial part of the kernel series was accepted to net-next tree and reached mainline as part of the 5.6 merge window (so that it's going to appear in `v5.6-rc1`. What is in mainline at the moment allows netlink based implementation of * `ethtool <dev>` * `ethtool s <dev> ...` * `ethtool -P <dev>` (using rtnetlink) and corresponding notifications. The userspace ethtool counterpart, however, will need a lot of work to make it ready for upstream submission. As it is highly desirable to have it in ethtool 5.6 release, this is going to be the primary focus at least for the first part of Hackweek 19.
 
×
Reply to mkubecek
Status update before Hackweek 19
After few more review rounds and rewrites, initial part of the kernel series was accepted to net-next tree and reached mainline as part of the 5.6 merge window (so that it's going to appear in v5.6-rc1. What is in mainline at the moment allows netlink based implementation of
• ethtool <dev>
• ethtool s <dev> ...
• ethtool -P <dev> (using rtnetlink)
and corresponding notifications.
The userspace ethtool counterpart, however, will need a lot of work to make it ready for upstream submission. As it is highly desirable to have it in ethtool 5.6 release, this is going to be the primary focus at least for the first part of Hackweek 19.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  about 4 years ago by mkubecek | Reply

  Status update after Hackweek 19

  TL;DR: The primary goal was achieved (12 minutes before the end of the week ).

  Summary of the Hackweek 19 progress:

  • abstractions for netlink socket and message buffer separated from struct nl_context
  • rework the code generating multiple messages from one set of parameters (for ethtool -s)
  • rework "char bitset" parser (for ethtool -s <dev> wol ...)
  • drop bitfield32 helpers and other code no longer used
  • compatibility with existing test suite (make check succeeds now)
  • split some too long patches
  • some bugs fixed
  • lot of style cleanups
  • more comments and better commit messages
  • cover letter
  • current work in progress tracked on github again

  The resulting series has been submitted to upstream.

×
Edit Comment 4776
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
#### Status update after Hackweek 19 TL;DR: The primary goal was achieved (12 minutes before the end of the week :smiley: ). Summary of the Hackweek 19 progress: * abstractions for netlink socket and message buffer separated from `struct nl_context` * rework the code generating multiple messages from one set of parameters (for `ethtool -s`) * rework "char bitset" parser (for `ethtool -s <dev> wol ...`) * drop bitfield32 helpers and other code no longer used * compatibility with existing test suite (`make check` succeeds now) * split some too long patches * some bugs fixed * lot of style cleanups * more comments and better commit messages * cover letter * current work in progress tracked [on github](https://github.com/mkubecek/ethnl) again The resulting series has been [submitted to upstream](http://lkml.kernel.org/r/cover.1581892124.git.mkubecek@suse.cz).
 
×
Reply to mkubecek
Status update after Hackweek 19
TL;DR: The primary goal was achieved (12 minutes before the end of the week ).
Summary of the Hackweek 19 progress:
• abstractions for netlink socket and message buffer separated from struct nl_context
• rework the code generating multiple messages from one set of parameters (for ethtool -s)
• rework "char bitset" parser (for ethtool -s <dev> wol ...)
• drop bitfield32 helpers and other code no longer used
• compatibility with existing test suite (make check succeeds now)
• split some too long patches
• some bugs fixed
• lot of style cleanups
• more comments and better commit messages
• cover letter
• current work in progress tracked on github again
The resulting series has been submitted to upstream.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview