On Thu, Jan 14, 2010 at 05:17:36PM +0900, KOSAKI Motohiro wrote:

quoted

quoted

Hmm..
Your answer didn't match I wanted.

Then I don't get what you want.

I want to know the benefit of the patch for patch reviewing.

quoted

quoted

few additional questions.

- Why don't you change your application? It seems natural way than kernel change.

There is no way to change my application and achieve what I've described
in a multithreaded app.

Then, we don't recommend to use mlockall(). I don't hope to hear your conclusion,
it is not objectivization. I hope to hear why you reached such conclusion.

So what do you recommend? Don't just wave hand on me saying "These
aren't the droids you're looking for". I explained you what I need to
achieve you seems to be trying to convince me I don't really need it
without proposing any alternatives. This is not constructive discussion.

quoted

quoted

- Why do you want your virtual machine have mlockall? AFAIK, current majority
  virtual machine doesn't.

It is absolutely irrelevant for that patch, but just because you ask I
want to measure the cost of swapping out of a guest memory.

No. if you stop to use mlockall, the issue is vanished.

And emulator parts will be swapped out too which is not what I want.
 

quoted

quoted

- If this feature added, average distro user can get any benefit?

?! Is this some kind of new measure? There are plenty of much more
invasive features that don't bring benefits to an average distro user.
This feature can bring benefit to embedded/RT developers.

I mean who get benifit?

Someone who wants to mlock all application memory, but wants to be able
to mmap big file for reading and understand that access to that file can
cause major fault. 

quoted

quoted

I mean, many application developrs want to add their specific feature
into kernel. but if we allow it unlimitedly, major syscall become
the trushbox of pretty toy feature soon.

And if application developer wants to extend kernel in a way that it
will be possible to do something that was not possible before why is
this a bad thing? I would agree with you if for my problem was userspace
solution, but there is none. The mmap interface is asymmetric in regards
to mlock currently. There is MAP_LOCKED, but no MAP_UNLOCKED. Why
MAP_LOCKED is useful then?

Why? Because this is formal LKML reviewing process. I'm reviewing your
patch for YOU.

I appreciate that, but unfortunately it seems that you are trying to dismiss
my arguments on the basis that _you_ don't find that useful.

If there is no objective reason, I don't want to continue reviewing.

--
			Gleb.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>