linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Metzmacher <metze@samba.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Steve French" <smfrench@gmail.com>,
	"Björn JACKE" <bjacke@samba.org>,
	CIFS <linux-cifs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] cifs fixes
Date: Sat, 20 Feb 2021 00:48:29 +0100	[thread overview]
Message-ID: <16240efc-64e4-2602-8ad3-98c1621dd015@samba.org> (raw)
In-Reply-To: <CAHk-=whOXR8ha7Zjzn2UPM8Ka-X1VSY7R07Pv-Fxeb3iKjKK3A@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1243 bytes --]

Hi Linus,

>> Do you know about the Zen3 status, I was thinking to replace the system
>> by this one with AMD Ryzen 9 5950X:
> 
> I have heard nothing but good things about Zen3 so far (apart from
> apparently people complaining about availability), but it's only been
> out a few months, so obviously coverage is somewhat limited.
> 
> I wish AMD hadn't decimated their Linux team (several years ago), and
> they definitely had some embarrassing issues early on with Zen (apart
> from the Zen 1 stability issues, they've screwed up rdrand at least
> three times, iirc). But I've yet to hear of any Zen 3 issues, and I
> suspect I'll upgrade when Threadripper comes out (I've become quite
> spoiled by the build speeds of my Threadripper 3970X - the only thing
> I miss is the better 'perf' support from Intel PEBS).
> 
> Note that I'm not necessarily the person who would hear about any
> issues first, though, so take the above with a pinch of salt.

Thanks for the hints! While we're waiting for the Ryzen 9 5950X machine
to get ready, I upgraded the Ryzen Threadripper 2950X to a 5.10 kernel
and we didn't had a freeze yet again.

Do you think 5.10 would be good for the Ryzen 9 5950X too?

Thanks!
metze




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-02-19 23:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 18:15 [GIT PULL] cifs fixes Steve French
2021-02-12 20:04 ` Linus Torvalds
2021-02-12 20:39   ` Steve French
2021-02-13  0:26     ` Stefan Metzmacher
2021-02-13  1:02       ` Linus Torvalds
2021-02-13  1:08         ` Stefan Metzmacher
2021-02-13  1:28           ` Linus Torvalds
2021-02-19 23:48             ` Stefan Metzmacher [this message]
2021-02-12 21:33   ` Steve French
2021-02-13 20:03 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2021-07-10 17:22 [GIT PULL] CIFS Fixes Steve French
2021-07-10 19:08 ` pr-tracker-bot
2021-03-10  2:49 [GIT PULL] cifs fixes Steve French
2021-03-10 18:13 ` pr-tracker-bot
2021-02-06 18:28 Steve French
2021-02-06 23:33 ` pr-tracker-bot
2020-05-17  2:45 [GIT PULL] CIFS Fixes Steve French
2020-05-17  4:45 ` pr-tracker-bot
2015-04-03  3:32 Steve French
2015-02-04 17:42 Steve French
2014-12-29 20:55 Steve French
2014-12-09 15:18 Steve French
     [not found] ` <CAH2r5muu_0byHxGJeKxmFinRSv4Aiduj=7U5ysyP-3MzK7e+HQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-10 23:40   ` Linus Torvalds
     [not found]     ` <CA+55aFzSTqAHhQSUjgQ+6wfD+q614SbEhQuBYhfUaQsmAmGrkQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-11  0:00       ` Steve French
2014-08-20 16:54 Steve French

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16240efc-64e4-2602-8ad3-98c1621dd015@samba.org \
    --to=metze@samba.org \
    --cc=bjacke@samba.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smfrench@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).