** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785816
Title:
Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING
To manage notifications about this bug go to:
https://bugs.launchp
This bug was fixed in the package linux - 4.15.0-46.49
---
linux (4.15.0-46.49) bionic; urgency=medium
* linux: 4.15.0-46.49 -proposed tracker (LP: #1814726)
* mprotect fails on ext4 with dax (LP: #1799237)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
* kernel
This bug was fixed in the package linux - 4.15.0-46.49
---
linux (4.15.0-46.49) bionic; urgency=medium
* linux: 4.15.0-46.49 -proposed tracker (LP: #1814726)
* mprotect fails on ext4 with dax (LP: #1799237)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
* kernel
Hi Mark,
According to comment
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/comments/8,
the systemd-networkd issue has been isolated to systemd and verified
that it's not a regression introduced by kernel 4.15.0-46-generic.
So considering the assessment of bug #1818340 and the pr
Timestamping seems to be working. However there may be other networking
issues in -proposed that could be kernel related (captured in bug
#1818340) that might warrant a hold on promotion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Mark, if you want to kick the tires on this capability before it goes
out, we're planning to release early next week, just FYI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785816
Title:
Consider
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785816
Title:
Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING
To ma
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785816
Title:
Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING
To manage notifications about
This bug was fixed in the package linux - 4.17.0-9.10
---
linux (4.17.0-9.10) cosmic; urgency=medium
* linux: 4.17.0-9.10 -proposed tracker (LP: #1787988)
* Cosmic update to 4.17.17 stable release (LP: #1787973)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
-
@Colin, thank you for posting your findings in comment #6.
If I am reading the spreadsheet correctly, it seems like the majority of
the time the CONFIG_NETWORK_PHY_TIMESTAMPING enabled kernel is on
average using fewer instructions and branches for the server side
(yellow cells H27-K36 and H65-K74)
** Description changed:
+ SRU Justification
+
+ Impact: CONFIG_NETWORK_PHY_TIMESTAMPING is disabled, preventing PTP time
+ synchronization using the DP83640 PHYTER.
+
+ Fix: Enable this option and set CONFIG_DP83640_PHY=m to enable the
+ DP83640 PHYTER driver.
+
+ Regression Potential: The kcon
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Seth
Hi Seth, 18.04 LTS is plenty for my purposes and for users wanting to
kick the tires on the functionality. No need for a backport on the
change at this stage.
Thank you!
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Committed to cosmic.
Mark, I'm assuming this should also go into 18.04. Is it wanted in the
16.04 GA kernel as well?
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785816
Title:
Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING
To manage notifications about
Colin, thanks for the analysis.
No rush on the change.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785816
Title:
Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING
To manage notifications
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785816
Title:
Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING
To manage notifica
@Seth, would you be so kind to as to enable this given the evidence
above?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785816
Title:
Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING
To manage n
With config CONFIG_NETWORK_PHY_TIMESTAMPING enabled, the calls to
skb_clone_tx_timestamp() and skb_defer_rx_timestamp() are enabled (these
normally are empty inlined no-op functions). The overhead from what I
can see is very small, for example for the tx path:
static unsigned int classify(const s
Thanks Colin. Yes, I'll get our configs updated.
** Changed in: linux (Ubuntu)
Assignee: Colin Ian King (colin-king) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17858
There's some extra code that's added universally, and more code if a PHY
which supports timestamping is present (currently only the DP83640
PHYTER device looks to be enabled by this option). What's done in the
PHY-specific code depends on whether or not timestamping is enabled. So
it's not complete
Thanks folks, looking forward to the results. I would have thought it
would noop where the feature was not in use; as far as I know it
requires explicit activation.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
I'll rig up some test scenarios and measure the overhead.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785816
We don't have any reason noted for having that option disabled. But
based on the kconfig help text I'd guess that it's because it adds
overhead to all network activity:
This allows timestamping of network packets by PHYs with
hardware timestamping capabilities. This option adds
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
26 matches
Mail list logo
