Jump to content


Gameplay about to take an FPS hit

not the fault of WG Intel only machines not AMD not WG fault Intel only not AMD

  • Please log in to reply
4 replies to this topic

arthurwellsley #1 Posted 03 January 2018 - 10:28 AM

    Major

  • Player
  • 51268 battles
  • 2,814
  • [-B-C-] -B-C-
  • Member since:
    05-11-2011

It would appear that for the last ten years Intel have been producing chips with an architecture that has a flaw. Windows is about to release a major patch to fix it. However, the patch will mean that the affected computers will run slower. Or at least that is the way I am reading the news article.

 

Source = https://www.theregis...pu_design_flaw/


Edited by arthurwellsley, 03 January 2018 - 10:28 AM.


jack_timber #2 Posted 03 January 2018 - 10:40 AM

    Lieutenant

  • Player
  • 32507 battles
  • 1,899
  • Member since:
    07-26-2014

Just as well I have an AMD CPU in desktop then, will give it a go on the I7 laptop when it gets upgraded though to see if it makes a difference.

Don't know if you skimmed the article but there is an "interesting" acronym that me thinks would be edited if I tried to post.

 



xtrem3x #3 Posted 03 January 2018 - 10:51 AM

    Second Lieutenant

  • Player
  • 31657 battles
  • 1,354
  • [EFE-X] EFE-X
  • Member since:
    01-03-2013
This game barely uses 15% of my almost 5 year old i7 4790k so I doubt it'll get an fps hit

Aikl #4 Posted 03 January 2018 - 10:59 AM

    Brigadier

  • Player
  • 25167 battles
  • 4,253
  • [-MM] -MM
  • Member since:
    04-13-2011

View Postjack_timber, on 03 January 2018 - 09:40 AM, said:

(...)
Don't know if you skimmed the article but there is an "interesting" acronym that me thinks would be edited if I tried to post.

 

 

The fix is to separate the kernel's memory completely from user processes using what's called Kernel Page Table Isolation, or KPTI. At one point, Forcefully Unmap Complete Kernel With Interrupt Trampolines, aka FUCKWIT, was mulled by the Linux kernel team, giving you an idea of how annoying this has been for the developers.

 

:D



Pvt_Duffer #5 Posted 03 January 2018 - 01:02 PM

    Lieutenant Сolonel

  • Player
  • 16653 battles
  • 3,144
  • [WJDE] WJDE
  • Member since:
    05-11-2011

View PostAikl, on 03 January 2018 - 09:59 AM, said:

 

The fix is to separate the kernel's memory completely from user processes using what's called Kernel Page Table Isolation, or KPTI. At one point, Forcefully Unmap Complete Kernel With Interrupt Trampolines, aka FUCKWIT, was mulled by the Linux kernel team, giving you an idea of how annoying this has been for the developers.

 

:D

 

Leaves  your  0-Ring wide open to anyone who wants a rummage.

 






1 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users