lkml.org 
[lkml]   [2005]   [Mar]   [21]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [patch 1/2] fork_connector: add a fork connector
FromGuillaume Thouvenin <>
DateMon, 21 Mar 2005 09:23:51 +0100
On Thu, 2005-03-17 at 14:05 -0800, Jesse Barnes wrote:
> On Thursday, March 17, 2005 1:38 pm, Evgeniy Polyakov wrote:
> > The most significant part there - is requirement to store
> > u32 seq in each CPU's cache and thus flush cacheline +
> > invalidate/get from mem on each other cpus> > each time it is accessed, which is a big price.> > Same thing has to happen with the lock.  To put it simply, writing global 
> variables from multiple CPUs with anything other than very low frequency is 
> bad.> > > It is totally Guillaume's work - so he decides,> > I would recomend per cpu counters and processor's> > id in each message.> > And of course userspace should take care of misordered
> > messages.> > I personally prefer such mechanism.> > Yep, I agree.  Hopefully Guillaume will too :)

Sure, I agree and I will implement the per cpu counters solution with a
processor id in each message. 

Thank you very much Jesse and Evgeniy for your great help,
Best regards,

Guillaume

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:11    [from the cache]
©2003-2008