IETF Logo Mail Archive

Re: [iccrg] ICCRG meeting minutes

Michael Welzl <michawe@ifi.uio.no> Wed, 13 April 2016 07:53 UTC

Return-Path: <michawe@ifi.uio.no>
X-Original-To: iccrg@ietfa.amsl.com
Delivered-To: iccrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40E9312D8E9 for <iccrg@ietfa.amsl.com>; Wed, 13 Apr 2016 00:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.196
X-Spam-Level:
X-Spam-Status: No, score=-5.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nxKqzw1nPFUk for <iccrg@ietfa.amsl.com>; Wed, 13 Apr 2016 00:53:54 -0700 (PDT)
Received: from mail-out5.uio.no (mail-out5.uio.no [IPv6:2001:700:100:10::17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B97DD12D9A1 for <iccrg@irtf.org>; Wed, 13 Apr 2016 00:53:54 -0700 (PDT)
Received: from mail-mx1.uio.no ([129.240.10.29]) by mail-out5.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1aqFcT-0001YA-Tz; Wed, 13 Apr 2016 09:53:49 +0200
Received: from boomerang.ifi.uio.no ([129.240.68.135]) by mail-mx1.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.80) (envelope-from <michawe@ifi.uio.no>) id 1aqFcT-0002qx-C4; Wed, 13 Apr 2016 09:53:49 +0200
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <20160413064335.GR31516@strugglingcoder.info>
Date: Wed, 13 Apr 2016 09:53:48 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <39FEC041-21B1-4EFA-B160-ED0809905392@ifi.uio.no>
References: <CAGD1bZaijEKEqXLaLfnCZ28vpnw7ogPO9Nsc+O=02q1w0hDY=A@mail.gmail.com> <20160412221530.GP31516@strugglingcoder.info> <3F408D90-6241-4564-9A55-126BB5022B04@lurchi.franken.de> <20160413064335.GR31516@strugglingcoder.info>
To: hiren panchasara <hiren@strugglingcoder.info>
X-Mailer: Apple Mail (2.2104)
X-UiO-SPF-Received:
X-UiO-Ratelimit-Test: rcpts/h 11 msgs/h 6 sum rcpts/h 13 sum msgs/h 6 total rcpts 40356 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-6.5, required=5.0, autolearn=disabled, RP_MATCHES_RCVD=-1.536, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: F4833C47D1EF2D9381221AD0C697A490D4BB4821
X-UiO-SPAM-Test: remote_host: 129.240.68.135 spam_score: -64 maxlevel 80 minaction 2 bait 0 mail/h: 6 total 9646 max/h 17 blacklist 0 greylist 0 ratelimit 0
Archived-At: <http://mailarchive.ietf.org/arch/msg/iccrg/2w4EsLqfneaNfvg_WlYbjyUT6xc>
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, iccrg@irtf.org, Jana Iyengar <jri@google.com>
Subject: Re: [iccrg] ICCRG meeting minutes
X-BeenThere: iccrg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussions of Internet Congestion Control Research Group \(ICCRG\)" <iccrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/iccrg>, <mailto:iccrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iccrg/>
List-Post: <mailto:iccrg@irtf.org>
List-Help: <mailto:iccrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/iccrg>, <mailto:iccrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2016 07:53:57 -0000

> On 13 Apr 2016, at 08:43, hiren panchasara <hiren@strugglingcoder.info> wrote:
> 
> On 04/13/16 at 06:59P, Michael Tuexen wrote:
>> 
>>> On 13 Apr 2016, at 00:15, hiren panchasara <hiren@strugglingcoder.info> wrote:
>>> 
>>> On 04/12/16 at 05:14P, Jana Iyengar wrote:
>>>> Hi all,
>>>> 
>>>> The minutes of the ICCRG meeting at IETF95 are now posted
>>>> <https://www.ietf.org/proceedings/95/minutes/minutes-95-iccrg>. Please send
>>>> corrections to the list or to the chairs.
>>>> 
>>>> Thanks much, Gorry, for taking these down!
>>> 
>>> Thanks for the notes. 
>>> 
>>> It'd be awesome if I can get a clarification in following though:
>>> 
>>> From - Michael Welzl: TCP in UDP (draft-welzl-irtf-iccrg-tcp-in-udp-00)
>>> Michael Tuexen: How do you ensure the right sequence of UDP packets and
>>> TCP-in-UDP packets on the server side, when using multicore systems?
>>> Michael: In our cases this worked.
>>> 
>>> Was there more discussed and is missed in the notes? Can Michael Welzl or
>>> someone else elaborate?
>> My point was that some NICs distribute incoming packets to multiple
>> threads and that the TCP/IP and TCP/UDP/IP might end up in different
>> threads. So it is hard to ensure sequence preservation in that case.
>> If you only use a single thread, there might be no issue.
>> 
>> I think a couple of other agreed that this is an issue and we stopped
>> discussing it.
> 
> I do understand the problem. I was wondering if there was any discussion
> towards possible solutions specific to this draft/work.
> 
> Thanks for clarifying.

Maybe my answer was written down too briefly, or the problem is that it didn't reflect my facial expression and overall reaction: in our case this worked because we didn't have a multicore system.
I'll fix the minutes to say: "in our case this worked, but we didn't have a multicore system".


I don't get the problem but I'm sure this only means that I don't understand enough about packet processing in multicore systems.

Cheers,
Michael

v2.23.0 | Report a Bug | By Email