On Wed, Aug 17, 2022 at 12:37:52AM -0500, Scott Cheloha wrote:
> On Wed, Aug 17, 2022 at 02:28:14PM +1000, Jonathan Gray wrote:
> > On Tue, Aug 16, 2022 at 11:53:51AM -0500, Scott Cheloha wrote:
> > > On Sun, Aug 14, 2022 at 11:24:37PM -0500, Scott Cheloha wrote:
> > > >
> > > > In the future when
Miod Vallat wrote:
> Come to think further about it, I think it is better for diskmap to
> always trust disk drivers to either :
> - not have any label (dk_label == NULL, or points to zeroed memory)
> or
> - have a valid label (duid is not zeroes).
What is the result if root runs disklabel, and
Come to think further about it, I think it is better for diskmap to
always trust disk drivers to either :
- not have any label (dk_label == NULL, or points to zeroed memory)
or
- have a valid label (duid is not zeroes).
The following diff thus relaxes the logic to always trust
dk_label->d_uid, unl
On Wed, Aug 17, 2022 at 02:28:14PM +1000, Jonathan Gray wrote:
> On Tue, Aug 16, 2022 at 11:53:51AM -0500, Scott Cheloha wrote:
> > On Sun, Aug 14, 2022 at 11:24:37PM -0500, Scott Cheloha wrote:
> > >
> > > In the future when the LAPIC timer is run in oneshot mode there will
> > > be no lapic_dela
broken after rev 1.652 of machdep.c
cpu0: Intel(R) Pentium(R) M processor 1200MHz ("GenuineIntel" 686-class) 1.20
GHz, 06-09-05
cpu0: Intel(R) Pentium(R) M processor 1200MHz ("GenuineIntel" -class) 1.20 GHz,
06-09-05
CPUCLASS_* can't be renumbered as machdep.c assumes class is
family - 3 in at
On Tue, Aug 16, 2022 at 11:53:51AM -0500, Scott Cheloha wrote:
> On Sun, Aug 14, 2022 at 11:24:37PM -0500, Scott Cheloha wrote:
> >
> > In the future when the LAPIC timer is run in oneshot mode there will
> > be no lapic_delay().
> >
> > [...]
> >
> > This is *very* bad for older amd64 machines,
On Tue, Aug 16, 2022 at 11:53:51AM -0500, Scott Cheloha wrote:
> On Sun, Aug 14, 2022 at 11:24:37PM -0500, Scott Cheloha wrote:
> >
> > In the future when the LAPIC timer is run in oneshot mode there will
> > be no lapic_delay().
> >
> > [...]
> >
> > This is *very* bad for older amd64 machines,
> after a prompt from stsp@ and florian@, reporting that newfs_msdos
> fails when given an $duid.i argument, I set down to see what could be
> going on. My test using an USB stick failed to reprdouce the problem.
> Then I started using a vnd, and that shows the issue (once in a
> while). The feelin
On Tue, Aug 16, 2022 at 09:43:48AM -0400, Josiah Frentsos wrote:
> Index: ssh-keygen.1
> ===
> RCS file: /cvs/src/usr.bin/ssh/ssh-keygen.1,v
> retrieving revision 1.224
> diff -u -p -r1.224 ssh-keygen.1
> --- ssh-keygen.1 11 Aug 2
On Tue, Aug 16, 2022 at 06:21:55AM -0300, Fernando Gont wrote:
> > Of course mbuf tags kill performance, but who uses hop-by-hop options
> > anyway? pf drops such packets per default.
>
> FWIW, HBH options are *themselves* known to kill performance. :-) (see:
> RFC9098).
Thanks for the link to
On Sun, Aug 14, 2022 at 11:24:37PM -0500, Scott Cheloha wrote:
>
> In the future when the LAPIC timer is run in oneshot mode there will
> be no lapic_delay().
>
> [...]
>
> This is *very* bad for older amd64 machines, because you are left with
> i8254_delay().
>
> I would like to offer a less a
OK?
Index: vnconfig.c
===
RCS file: /cvs/src/sbin/vnconfig/vnconfig.c,v
retrieving revision 1.7
diff -u -p -r1.7 vnconfig.c
--- vnconfig.c 25 Oct 2021 19:54:29 - 1.7
+++ vnconfig.c 16 Aug 2022 14:01:29 -
@@ -78,11 +78,8
On Tue, Aug 16, 2022 at 07:46:22PM +1000, Jonathan Matthew wrote:
>
> 0x2522 was for the 16/32GB Optane Memory devices.
https://ark.intel.com/content/www/us/en/ark/products/99742/intel-optane-memory-series-32gb-m-2-80mm-pcie-3-0-20nm-3d-xpoint.html
https://www.intel.com/content/dam/www/public/us/
On Tue, Aug 16, 2022 at 10:11:03AM +0200, Andreas Bartelt wrote:
> On 8/16/22 05:22, Jonathan Gray wrote:
> > On Sun, Aug 14, 2022 at 04:03:59PM +0200, Andreas Bartelt wrote:
> > > Hi,
> > >
> > > Intel Optane 905p NVMe devices were not yet recognized in CURRENT (e.g.,
> > > https://ark.intel.com
Hi, Alexander,
On 13/8/22 16:08, Alexander Bluhm wrote:
[...]
Of course mbuf tags kill performance, but who uses hop-by-hop options
anyway? pf drops such packets per default.
FWIW, HBH options are *themselves* known to kill performance. :-) (see:
RFC9098).
OTOH, MLD uses HBH. But for the
On 8/16/22 05:22, Jonathan Gray wrote:
On Sun, Aug 14, 2022 at 04:03:59PM +0200, Andreas Bartelt wrote:
Hi,
Intel Optane 905p NVMe devices were not yet recognized in CURRENT (e.g.,
https://ark.intel.com/content/www/us/en/ark/products/148607/intel-optane-ssd-905p-series-380gb-m-2-110mm-pcie-x4-
16 matches
Mail list logo