linux-kernel - Re: [PATCH] Implementation of the sendgroup() system call

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090504093254.196227ivc4tb4k9w@www.nexusmail.uwaterloo.ca>
Date:	Mon, 04 May 2009 09:32:54 -0400
From:	Elad Lahav <elahav@...uwaterloo.ca>
To:	Eric Dumazet <dada1@...mosbay.com>
Cc:	Elad Lahav <elahav@...terloo.ca>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Implementation of the sendgroup() system call

> ie using a different syscall to setup the group (and compute/lookup  
> all needed routes)
>   (this syscall would be able to add/delete members (with their  
> footer/header) to socket group)
This was the original implementation, but it turned out to be less  
effective for several reasons:
1. Groups that change frequently result in too many system calls for  
managing the group (think of users joining and leaving a live  
broadcast);
2. Allowing the caller to maintain the group is more flexible than  
having the kernel responsible for it;
3. No support for per-call per-recipient data.

Point 3 is useful in some scenarios, such as multiplayer online games,  
where the bulk of the data is shared, but each player also receives a  
small chunk of dedicated information.

--Elad




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