From owner-freebsd-arch@FreeBSD.ORG Tue Jan 8 19:02:40 2008 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FE5916A418; Tue, 8 Jan 2008 19:02:40 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id B3CC813C458; Tue, 8 Jan 2008 19:02:37 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail2.internal.cacheflow.com (bcs-mail2.internal.cacheflow.com [10.2.2.59]) by whisker.bluecoat.com (8.13.8/8.13.8) with ESMTP id m08IkkkN029628; Tue, 8 Jan 2008 10:46:47 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 8 Jan 2008 10:46:42 -0800 Message-ID: <305C539CA2F86249BF51CDCE8996AFF4096E123E@bcs-mail2.internal.cacheflow.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: resend: multiple routing table roadmap (format fix) Thread-Index: AchQp56/Ql+VUKdpSjGv0EsTFz+khQBfunIg References: <4772F123.5030303@elischer.org> <477416CC.4090906@elischer.org> <477D2EF3.2060909@elischer.org><4780E5E7.2070202@FreeBSD.org> <4781197F.1000105@elischer.org> From: "Li, Qing" To: "Vadim Goncharov" , "Julian Elischer" , "Bruce M. Simpson" Cc: arch@freebsd.org, Ivo Vachkov , Robert Watson , FreeBSD Net , Qing Li Subject: RE: resend: multiple routing table roadmap (format fix) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2008 19:02:40 -0000 >=20 > Surely, routing table should contain a cached pointer to an=20 > entry in L2 table (ARP in case of Ethernet), to not do double=20 > lookups. But still separate those tables... >=20 The routing table contains only the interface route, from this interface route the L2 table is accessed for on net hosts. So it's a one-to-many relationship. How do you propose the L2 entry caching be done ? -- Qing