Thanks for the reply! This helps a lot.
Best,
Zhiting
On Thu, Mar 14, 2019 at 3:33 AM Gleb Natapov wrote:
> On Wed, Mar 13, 2019 at 04:59:33PM -0500, zhiting zhu wrote:
> > If I understand what you said correctly, OSv's read/write does go through
> > the pagecache (the one implemented in
Ideally, the build shouldn't care what is the pathname of the build
directory. But some parts of the build process use, for historical
reasons and for convenience, full pathnames, and some of that code did
not correctly handle the case where the pathname might contain spaces,
and the build fails.
From: Nadav Har'El
Committer: Nadav Har'El
Branch: master
scripts/build: gracefully handle spaces in image= parameter
A space in the image= or modules= parameter, while not really useful,
should not cause strange errors messages about bad parameters to module.py.
Quoting was missing.
On Wed, Mar 13, 2019 at 04:59:33PM -0500, zhiting zhu wrote:
> If I understand what you said correctly, OSv's read/write does go through
> the pagecache (the one implemented in core/pagecache.cc).
> In read, a page is allocated and there's a thread that copies the read page
> into ARC
On Thu, Mar 14, 2019 at 5:09 AM Waldek Kozaczuk
wrote:
>
>
> On Tuesday, March 12, 2019 at 7:26:45 AM UTC-4, Nadav Har'El wrote:
>>
>>
>> On Tue, Mar 12, 2019 at 4:43 AM Commit Bot
>> wrote:
>>
>>> From: Waldemar Kozaczuk
>>> Committer: Waldemar Kozaczuk
>>> Branch: master
>>>
>>> Lowered
Hi,
On Thu, Mar 14, 2019 at 5:11 AM Waldek Kozaczuk
wrote:
> I wonder if anyone has had chance to read this paper. I would like to see
> what others think about reasons OSv thread scheduler does not scale well
> with number of vCPUs.
>
I am not sure that the scheduler is to blame here.
It is
