From: Richard Weinberger <richard@nod.at>
To: anton ivanov <anton.ivanov@cambridgegreys.com>
Cc: hch <hch@lst.de>, Johannes Berg <johannes@sipsolutions.net>,
linux-um <linux-um@lists.infradead.org>
Subject: Re: [PATCH, RFC] um: remove set_fs
Date: Fri, 27 Aug 2021 00:04:20 +0200 (CEST) [thread overview]
Message-ID: <1948049684.7020.1630015460699.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <50ef0553-6b9f-32b4-3ee9-20464c01d634@cambridgegreys.com>
----- Ursprüngliche Mail -----
> Von: "anton ivanov" <anton.ivanov@cambridgegreys.com>
> An: "richard" <richard@nod.at>
> CC: "hch" <hch@lst.de>, "Johannes Berg" <johannes@sipsolutions.net>, "linux-um" <linux-um@lists.infradead.org>
> Gesendet: Donnerstag, 26. August 2021 23:12:32
> Betreff: Re: [PATCH, RFC] um: remove set_fs
> On 26/08/2021 20:15, Richard Weinberger wrote:
>> ----- Ursprüngliche Mail -----
>>>> In other words - very little generated code actually changes with
>>>> this patch, except for the context switch path, which gets simplified.
>>>
>>> I am going to test it and play with it later.
>>
>> Did it survive your testing?
>> The changes look sane to me.
>>
>> Thanks,
>> //richard
>>
>
> Does not crash, does not show any substantial differences in performance.
Sounds like a decent patch. :-)
> I am OK with it.
So, let's be keen and merge it.
Thanks,
//richard
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2021-08-26 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 13:38 [PATCH, RFC] um: remove set_fs Christoph Hellwig
2021-07-09 14:47 ` Johannes Berg
2021-07-09 16:57 ` Christoph Hellwig
2021-08-23 7:04 ` Christoph Hellwig
2021-08-23 7:14 ` Anton Ivanov
2021-08-23 8:28 ` Anton Ivanov
2021-08-23 12:17 ` Christoph Hellwig
2021-08-23 12:29 ` Anton Ivanov
2021-08-26 19:15 ` Richard Weinberger
2021-08-26 21:12 ` Anton Ivanov
2021-08-26 22:04 ` Richard Weinberger [this message]
2021-08-27 5:40 ` hch
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=1948049684.7020.1630015460699.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=anton.ivanov@cambridgegreys.com \
--cc=hch@lst.de \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.