Sponsored Content
The Lounge War Stories Linus Torvalds reply about Meltdown and Spectre. Post 303011891 by wisecracker on Thursday 25th of January 2018 05:34:25 AM
Old 01-25-2018
Quote:
Originally Posted by dodona
.. for a only hypothetical problem.
Perhaps, perhaps not; a hardware design problem that goes back decades just to get performance figures to sell their CPUs is more than bad to say the least - especially when the manufacturers knew about it.
Also, it can't be that hypothetical if it has been proven to work. It is the big/gigantic sytems that will be affected by these patches not so much the piffling little stuff like my MacBook Pro. I can handle a performance hit knowing about it now but can the big guns? <- Rhetorical!

But unless one has experience of writing kernels and OSes then one can't possibly know how difficult it is to create patches, (that will inherently give a performance hit just to _correct_ a deliberate manufacturing fault for profit), that will not slow things down too much.
 

5 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

What the best HD format for Unix & Linus

Hello people, Im just about to install linux and unix but would like to know what the best Partition type format is for both of them. Can anyone tell me Thankyou in advanced (1 Reply)
Discussion started by: jeffersno1
1 Replies

2. Filesystems, Disks and Memory

hard disk meltdown

I had an issue with a second hard disk in my machine. I have a sparc station running solaris 7. It was working fine but now it wont mount on boot up and when you try to mount it manually it gives an I/O error. I tried a different disk as a control which was fine. What I want to know is if my... (3 Replies)
Discussion started by: Henrik
3 Replies

3. News, Links, Events and Announcements

A Couple of Short Linus Torvalds Videos

This link is to a page that has two short videos that feature Linus Torvalds discussing the Linux kernel. After you watch the first video, scroll down some more to reach the second video. (0 Replies)
Discussion started by: Perderabo
0 Replies

4. What is on Your Mind?

Meltdown and Spectre CPU bugs

This seems a bit serious: Meltdown, Spectre: The password theft bugs at the heart of Intel CPUs • The Register Vulnerability Note VU#584653 - CPU hardware vulnerable to side-channel attacks Project Zero: Reading privileged memory with a side-channel (8 Replies)
Discussion started by: Scrutinizer
8 Replies

5. AIX

AIX 6.1, POWER5 and Spectre/Meltdown

Apologies for this newbie question. We have inherited an IBM p5 520 (9111-520) running AIX 6.1.0.0 which seems to be the base install and no further patches installed. Is this vulnerable to the Spectre/Meltdown threat? Are patches available? Looks like AIX 6.1.0.0 went 'end of support' in... (8 Replies)
Discussion started by: the_garbage
8 Replies
GIT-PACK-REFS(1)						    Git Manual							  GIT-PACK-REFS(1)

NAME
git-pack-refs - Pack heads and tags for efficient repository access SYNOPSIS
git pack-refs [--all] [--no-prune] DESCRIPTION
Traditionally, tips of branches and tags (collectively known as refs) were stored one file per ref under $GIT_DIR/refs directory. While many branch tips tend to be updated often, most tags and some branch tips are never updated. When a repository has hundreds or thousands of tags, this one-file-per-ref format both wastes storage and hurts performance. This command is used to solve the storage and performance problem by stashing the refs in a single file, $GIT_DIR/packed-refs. When a ref is missing from the traditional $GIT_DIR/refs hierarchy, it is looked up in this file and used if found. Subsequent updates to branches always create new files under $GIT_DIR/refs hierarchy. A recommended practice to deal with a repository with too many refs is to pack its refs with --all --prune once, and occasionally run git pack-refs --prune. Tags are by definition stationary and are not expected to change. Branch heads will be packed with the initial pack-refs --all, but only the currently active branch heads will become unpacked, and the next pack-refs (without --all) will leave them unpacked. OPTIONS
--all The command by default packs all tags and refs that are already packed, and leaves other refs alone. This is because branches are expected to be actively developed and packing their tips does not help performance. This option causes branch tips to be packed as well. Useful for a repository with many branches of historical interests. --no-prune The command usually removes loose refs under $GIT_DIR/refs hierarchy after packing them. This option tells it not to. AUTHOR
Written by Linus Torvalds <torvalds@osdl.org[1]> GIT
Part of the git(1) suite NOTES
1. torvalds@osdl.org mailto:torvalds@osdl.org Git 1.7.1 07/05/2010 GIT-PACK-REFS(1)
All times are GMT -4. The time now is 02:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy