Date: Wed, 15 Apr 2015 15:02:03 +0200 From: Luigi Rizzo <rizzo@iet.unipi.it> To: Gleb Smirnoff <glebius@freebsd.org> Cc: "freebsd-net@freebsd.org" <net@freebsd.org> Subject: Re: moving ALTQ out of contrib Message-ID: <CA%2BhQ2%2BhzEOCs4gz3N3DtJ3AmD5E2_1Quc_OAcM=sir_7Dq1HXQ@mail.gmail.com> In-Reply-To: <20150415125944.GD883@glebius.int.ru> References: <20150414135346.GU883@FreeBSD.org> <20150415073823.GA94402@onelab2.iet.unipi.it> <20150415122627.GZ883@glebius.int.ru> <CA%2BhQ2%2BhLm9FvNJhnZrz4BytN1%2BTig=brgi07ZK7TUS9KKym82w@mail.gmail.com> <20150415125944.GD883@glebius.int.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 15, 2015 at 2:59 PM, Gleb Smirnoff <glebius@freebsd.org> wrote: > On Wed, Apr 15, 2015 at 02:53:34PM +0200, Luigi Rizzo wrote: > L> Then if you do sys/net/altq/ do you also plan to split the current > L> content of sys/net/ into separate subdirectories ? > L> > L> We currently have quite a few separate things in sys/net/, such as > L> - various bpf files > L> - generic ifnet support (including raw sockets) > L> - various libraries (compression and hash functions) > L> - routing code > L> - bridging code > L> - a ton of special ifnets, (tun, tap, epair, gif, ....) > L> - bridging code > L> that could benefit from a bit of partitioning > > I definitely agree that a) special interfaces b) lagg+lacp > c) generic libraries should be separated. I don't mind if anyone does > this job :) > > But I personally would prefer is this is done after the lifetime > of the projects/ifnet branch, since if stuff is moved while I work > on projects/ifnet, my merging will become a nightmare. I already have > conflicts quite often. > sure, there is no rush. I was just trying to understand why your preference is for sys/net/altq instead of sys/netaltq as we have for other components. thanks again luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BhQ2%2BhzEOCs4gz3N3DtJ3AmD5E2_1Quc_OAcM=sir_7Dq1HXQ>