Re: [PATCH] vmpressure: implement strict mode

[Pavel Machek]

On Tue 2013-07-02 11:06:28, Luiz Capitulino wrote:
> On Mon, 1 Jul 2013 10:51:03 +0200
> Pavel Machek <pavel@xxxxxx> wrote:
> 
> > Hi!
> > 
> > > diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
> > > index ddf4f93..3c589cf 100644
> > > --- a/Documentation/cgroups/memory.txt
> > > +++ b/Documentation/cgroups/memory.txt
> > > @@ -807,12 +807,14 @@ register a notification, an application must:
> > >  
> > >  - create an eventfd using eventfd(2);
> > >  - open memory.pressure_level;
> > > -- write string like "<event_fd> <fd of memory.pressure_level> <level>"
> > > +- write string like "<event_fd> <fd of memory.pressure_level> <level> [strict]"
> > >    to cgroup.event_control.
> > >  
> > 
> > This is.. pretty strange interface. Would it be cleaner to do ioctl()?
> > New syscall?
> 
> Are you referring to my new mode or to the whole thing?

Well. The interface was already very strange and you made it even
worse.

For example... How is the string terminated? \0? \n? Not at all? Needs
to be written in single write? How many spaces are allowed? Can I put
there \t? How many leading zeros? How do you know that you can stop
looking for "strict" string?

Dunno. Passing fd by writting it out in ascii is strange. (And writing
fd in ascii to the same fd is ... very strange.)

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/