Hi Kamezawa-san,
> On Thu, 21 May 2009 19:36:06 +0900 (JST)
> Ryo Tsuruta wrote:
>
> > Hi Kamezawa-san and Kosaki-san,
> >
> > > > I have a suggestion for css_id numbering. How about using the same
> > > > numbering scheme as process ID for css_id instead of idr? It prevents
> > > > the same ID
On Thu, 21 May 2009 19:36:06 +0900 (JST)
Ryo Tsuruta wrote:
> Hi Kamezawa-san and Kosaki-san,
>
> > > I have a suggestion for css_id numbering. How about using the same
> > > numbering scheme as process ID for css_id instead of idr? It prevents
> > > the same ID from being reused quickly.
> >
>
Hi Kamezawa-san and Kosaki-san,
> > I have a suggestion for css_id numbering. How about using the same
> > numbering scheme as process ID for css_id instead of idr? It prevents
> > the same ID from being reused quickly.
>
> process ID is not "short"(2bytes).
>
> > blkio-cgroup can benefit from i
On Thu, 21 May 2009 16:30:38 +0900
KAMEZAWA Hiroyuki wrote:
> On Thu, 21 May 2009 16:28:59 +0900 (JST)
> Ryo Tsuruta wrote:
>
> > Hi Kamezawa-san,
> >
> > I have a suggestion for css_id numbering. How about using the same
> > numbering scheme as process ID for css_id instead of idr? It prevent
On Thu, 21 May 2009 16:28:59 +0900 (JST)
Ryo Tsuruta wrote:
> Hi Kamezawa-san,
>
> I have a suggestion for css_id numbering. How about using the same
> numbering scheme as process ID for css_id instead of idr? It prevents
> the same ID from being reused quickly.
process ID is not "short"(2bytes
> Hi Kamezawa-san,
>
> I have a suggestion for css_id numbering. How about using the same
> numbering scheme as process ID for css_id instead of idr? It prevents
> the same ID from being reused quickly.
> blkio-cgroup can benefit from it. If some pages still have an old ID,
> it can somewhat preve
