mt(1)/libmt: Add LTO-10 density codes and specs.
These were obtained from IBM specs and actual tapes/drives.
Standard LTO-10 cartriges hold 30TB raw, 75TB with 2.5:1 compression.
Premium LTO-10 cartridges hold 40TB raw, 100TB with 2.5:1 compression.
LTO-10 tape drives are not backward compatible with previous generation
LTO tapes. (This is a change from older generation drives.)
Since the Premium tape is a new thing for LTO, we'll call this density
code LTO-10P vs. the standard LTO-10. The barcode identifier for LTO-10
tapes is "LA"; the barcode identifier for LTO-10P tapes is "PA".
LTO-10 cartridges contain 1035m of tape, while LTO-10 Premium
cartridges contain 1337m of tape and have slightly higher density.
(Obtained from MAM data on actual tape cartridges and the density
report, obtained via 'mt getdensity'.) LTO-10 cartridges use a
polyethylene naphthalate (PEN) film substrate. LTO-10 Premium
cartridges use an Aramid (aromatic polyamide) substrate that is thinner
[12 lines not shown]
mt(1)/libmt: Add LTO-10 density codes and specs.
These were obtained from IBM specs and actual tapes/drives.
Standard LTO-10 cartriges hold 30TB raw, 75TB with 2.5:1 compression.
Premium LTO-10 cartridges hold 40TB raw, 100TB with 2.5:1 compression.
LTO-10 tape drives are not backward compatible with previous generation
LTO tapes. (This is a change from older generation drives.)
Since the Premium tape is a new thing for LTO, we'll call this density
code LTO-10P vs. the standard LTO-10. The barcode identifier for LTO-10
tapes is "LA"; the barcode identifier for LTO-10P tapes is "PA".
LTO-10 cartridges contain 1035m of tape, while LTO-10 Premium
cartridges contain 1337m of tape and have slightly higher density.
(Obtained from MAM data on actual tape cartridges and the density
report, obtained via 'mt getdensity'.) LTO-10 cartridges use a
polyethylene naphthalate (PEN) film substrate. LTO-10 Premium
cartridges use an Aramid (aromatic polyamide) substrate that is thinner
[12 lines not shown]
NAS-140248 / 26.0.0-BETA.2 / Force child smbd processes to reload SMB config (by anodos325) (#18436)
This commit alters the reload behavior for the cifs service plugin such
that we force all active SMB sessions to reload their share
configuration. This change is made to address issues whereby an
already-existing SMB session cannot tcon into newly-created shares.
Original PR: https://github.com/truenas/middleware/pull/18435
Co-authored-by: Andrew Walker <andrew.walker at truenas.com>
NAS-140248 / 27.0.0-BETA.1 / Force child smbd processes to reload SMB config (#18435)
This commit alters the reload behavior for the cifs service plugin such
that we force all active SMB sessions to reload their share
configuration. This change is made to address issues whereby an
already-existing SMB session cannot tcon into newly-created shares.
[AMDGPU][InstCombine] Fold unused m0 operand to poison for sendmsg intrinsics (#183755)
Fold the second operand (m0) of llvm.amdgcn.s.sendmsg and
llvm.amdgcn.s.sendmsghalt to poison when the message type does not use
m0.
Only MSG_GS_ALLOC_REQ (message ID 9) actually reads the m0 value. All
other message types ignore it, so we can fold the operand to poison,
which eliminates unnecessary s_mov_b32 m0, 0 instructions in the
generated code.
Fixes https://github.com/llvm/llvm-project/issues/183605
- Added InstCombine case for amdgcn_s_sendmsg and amdgcn_s_sendmsghalt
intrinsics
- Extract message ID using 8-bit mask to handle both pre-GFX11 (4-bit)
and GFX11+ (8-bit) encoding
- Only preserve m0 operand for ID_GS_ALLOC_REQ
[clang][ssaf] Add UnsafeBufferUsage summary extractor for functions (#182941)
The UnsafeBufferUsage summary extract reuses -Wunsafe-buffer-usage to
find all unsafe pointers in functions and translates them to
entity-based representation.
rdar://169191570
[DirectX] Specify element-aligned vectors
Use the new "ve" Data Layout specifier to indicate that vectors are
element-aligned for the target.
Part of #123968
[X86][llvm-exegesis] Add support for emeraldrapids (#185928)
We were seeing some test failures internally due to some of our
llvm-exegesis tests starting to run on emeraldrapids machines and
erroring because there was no mapping.
We simply mirror sapphirerapids here because libpfm does the same
internally and raptor cove (uarch for emeraldrapids) is just a refresh
of golden cove (uarch for sapphirerapids), so should not contain any
differences with regards to execution ports.
Force child smbd processes to reload SMB config
This commit alters the reload behavior for the cifs service
plugin such that we force all active SMB sessions to reload their
share configuration. This change is made to address issues whereby
an already-existing SMB session cannot tcon into newly-created
shares.