hello,

On 3/12/08, fooler mail <[EMAIL PROTECTED]> wrote:
> On Tue, Mar 11, 2008 at 11:23 PM, Edel SM <[EMAIL PROTECTED]> wrote:
>  > hello,
>  >
>  > On 3/11/08, fooler mail <[EMAIL PROTECTED]> wrote:
>  > > you cannot benefit the tcp offloading feature of a nic if you put this
>  > >  on your box acting as a router... the basic mechanism of a router is
>  > >  to route or forward packets based on the destination address... as the
>  > >  packets pass on the router... router will only decrease the ip
>  > >  header's ttl value, if the value is zero, it drops the packet and send
>  > >  icmp type 11 (time exceeded) back to the sender...  if the value is
>  > >  non-zero.. recompute and updates the checksum in the ip header and
>  > >  forwards on the next hop based on its routing table...
>  >
>  > but the NIC consumes cpu power while it process traffic, right? im
>  > just thinking of offloading (saving) cpu task and put it in the nic w/
>  > its onboard processor. cheap nics relies on main cpu power, while
>  > better (and expensive) ones have processor onboard.
>
>
> ill take you to a bigger picture... ill present you moore's law...
>  processing speed.. memory capacity.. bandwidth... etc.. increasingly
>  at exponential rates... your host's processor and memory buffer are
>  much efficient than your nic's processor and memory processing a
>  packet... with nic... you are limited to its processing speed and
>  memory buffer compare to your host's resources acting as a router...
>  although you can apply moore's law on nic... unlike with outgoing
>  packets where the host can temporarily put the packets on its big
>  buffer while the nic is busy but for incoming packets where if the
>  host is too slow fetching the packets from nic's buffer... the nic is
>  starting to drop the incoming packets when its buffer is full...
>  therefore it is much better to focus increasing the power of your host
>  rather than on your nic...

i have this setup currently:

                                                        +-----------------+
                             (frame-relay)     |                       |vlanB
                         +---telcoA-----------+ pc300
+------------ lan A
                         |                                |
          |vlanC
internet -------+                               |
+------------ lan B
                         |                               |
          |vlanN
                        +---telcoB-----------+vlanA
+------------- dmz X
                           (10mbps fiber)   |                       |
                                                        +----------------+
                                                            router

public servers are on public dmz, and internal hosts (database & fs)
are in internal dmz. office/building LANs are separated. i have less
than 10 vlans active, with more or less 300 hosts.

that work fine. but somtimes the pc router pauses/hang for a while if
there's so much traffic (FS file transfer, web uploading, etc).
sometimes hte NIC stops responding (hang?) and we need to reboot the
router. it may be also be a problem in the driver, switch, etc.

i use dlink nic, rtl8139 chipset. im just thinking replacing the nic
w/ a better one. and getting good nic. so that's why i asked. what do
you sugest?

>
>  that is why others say that tcp offloading engine embedded in a nic is
>  a dumb idea...
>

our LAN FS w/ eepro100 (onboard) perform so much better compared to
dlink/8139 nic (the host has extra/standby dlink nic). i have just
thought before that all nics are the same.

thanks.

>
>
>  fooler.
>  _________________________________________________
>  Philippine Linux Users' Group (PLUG) Mailing List
>  [email protected] (#PLUG @ irc.free.net.ph)
>  Read the Guidelines: http://linux.org.ph/lists
>  Searchable Archives: http://archives.free.net.ph
>

--edel
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph

Reply via email to