[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Porting and Extending a TCP/IP noise simulator from kernel 2.2.xto 2.4.x
- To: "Nadav Har'El" <nyh(at-nospam)math.technion.ac.il>
- Subject: Re: Porting and Extending a TCP/IP noise simulator from kernel 2.2.xto 2.4.x
- From: Shlomi Fish <shlomif(at-nospam)techst02.technion.ac.il>
- Date: Thu, 19 Jul 2001 11:54:48 +0300 (EEST)
- Cc: <linux-il(at-nospam)linux.org.il>
- Delivered-To: linux.org.il-linux-il@linux.org.il
- In-Reply-To: <20010719114229.A6908@leeor.math.technion.ac.il>
- Sender: linux-il-bounce(at-nospam)cs.huji.ac.il
On Thu, 19 Jul 2001, Nadav Har'El wrote:
> On Thu, Jul 19, 2001, Shlomi Fish wrote about "Re: Porting and Extending a TCP/IP noise simulator from kernel 2.2.x to 2.4.x":
> > > some parts were completely rewritten (e.g. the firewalling code). i think
> > > most changes that got to do with what u call 'multi-threaded processes' is
> > > actually not related to threads specifically - but to paralel execution in
> > > general - and got to do with having mroe fine-grained usage of locks
> > > inside the kernel, to allow taking better advantage of existance of
> > > seveval CPUs in SMP mode.
> > >
> >
> > No, the problem was that in kernel 2.2.x the TCP/IP stack was not
> > multi-threaded. That is a blocking accept() call would have blocked the
> > entire process, and if one thread sent data the other would get stuck,
> > etc. etc.
>
> As far as I understand, Guy was right, and your correction isn't. I have
> written multi-threaded communication programs running on kernels 2.2, and
> I never had problems like you describe. I don't remember if I used accept(),
> but I certainly used a blocking read(), select() and stuff like that, and
> multithreaded behavior was fine.
>
> ... SNIPPED
I'd like to terminate this sub-thread. It doesn't matter too much if the
TCP/IP stack of linux 2.2 was thread-enabled or not.
What is important is that there may be diffferences in the architecture
of the two series, and from commentary buy Guy Keren and OmerM I think it
may actually be much easier for me.
Regards,
Shlomi Fish
----------------------------------------------------------------------
Shlomi Fish shlomif@t2.technion.ac.il
Home Page: http://t2.technion.ac.il/~shlomif/
Home E-mail: shlomif@techie.com
A more experienced programmer does not make less bugs. He just realizes
what went wrong more quickly.
=================================================================
To unsubscribe, send mail to linux-il-request@linux.org.il with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail linux-il-request@linux.org.il