On Wed, Jan 06, 2021 at 10:27:42AM +0100, Claudio Jeker wrote:
> Linux and FreeBSD both support the use of struct ip_mreqn in
> IP_ADD_MEMBERSHIP and IP_DROP_MEMBERSHIP. This struct adds one more field
> to pass an interface index to the kernel (instead of using the IP
> address).
>
> struct
On Wed, Jan 06, 2021 at 10:27:42AM +0100, Claudio Jeker wrote:
> Linux and FreeBSD both support the use of struct ip_mreqn in
> IP_ADD_MEMBERSHIP and IP_DROP_MEMBERSHIP. This struct adds one more field
> to pass an interface index to the kernel (instead of using the IP
> address).
>
> struct
On Sun, Jan 03, 2021 at 11:40:42AM +0100, Denis Fondras wrote:
> Le Fri, Dec 11, 2020 at 10:53:56AM +, Olivier Cherrier a écrit :
> >
> > Hello tech@,
> >
> > Is there any interest for this feature to be commited?
> > I find it very useful. Thank you Denis!
> >
>
> Here is an up to
On Thu, Dec 24, 2020 at 12:25:40AM +0100, Patrick Wildt wrote:
> > On Fri, Dec 18, 2020 at 10:33:52PM +0100, Mark Kettenis wrote:
> >
> > > The diff below disables the optimized functions on little-endian
> > > architectures such that we always use rasops1_putchar(). This makes
> > > ssdfb(4)
Currently rpki-client keeps all pending work on a queue and only removes
it from the queue at once it got processed. The only bit that the parent
rpki-client process needs from the queue is the type when processing the
response. So instead of passing the id pass the type back from the parser.
> Date: Thu, 7 Jan 2021 14:24:58 +0100
> From: Frederic Cambus
>
> On Thu, Dec 24, 2020 at 12:25:40AM +0100, Patrick Wildt wrote:
>
> > > On Fri, Dec 18, 2020 at 10:33:52PM +0100, Mark Kettenis wrote:
> > >
> > > > The diff below disables the optimized functions on little-endian
> > > >
> On 7 Jan 2021, at 04:14, Klemens Nanni wrote:
>
> pair(4)'s output path can run without kernel lock just fine.
>
> NB: Looking at CVS log, it seems this was not done during import because
> IFXF_MPSSAFE became a thing afterwards.
>
> Feedback? Objections? OK?
>
Looks good to me.
ok mvs
>
On Thu, 7 Jan 2021 10:20:34 -0700
Thomas Frohwein wrote:
> On Wed, Jan 06, 2021 at 10:48:58PM +0100, Marcus Glocker wrote:
>
> [...]
>
> > The implementation as such looks fine to me.
> > But I quickly gave the diff a spin before on amd64 using my PS
> > controller, and the result is not what
On Thu, Jan 07, 2021 at 04:03:41PM +0100, Claudio Jeker wrote:
> Here is my try to extend ip(4) to also document struct ip_mreqn.
> Not sure what is the best way to document the option to use either struct
> ip_mreq or struct ip_mreqn with IP_ADD_MEMBERSHIP.
>
> --
> :wq Claudio
>
hi! comments
> Date: Thu, 7 Jan 2021 11:15:41 -0600
> From: Scott Cheloha
>
> Hi,
>
> I want to isolate statclock() from hardclock(9). This will simplify
> the logic in my WIP dynamic clock interrupt framework.
>
> Currently, if stathz is zero, we call statclock() from within
> hardclock(9). It looks
Hello,
sorry to come back after while...
On Tue, Jan 05, 2021 at 10:05:39PM +1000, David Gwynne wrote:
> On Mon, Jan 04, 2021 at 06:37:54PM +0100, Alexander Bluhm wrote:
> > On Mon, Jan 04, 2021 at 11:21:50PM +1000, David Gwynne wrote:
> > > this chunk pops out as a standalone change.
> > >
> >
On Sat, Dec 12, 2020 at 01:32:13PM -0600, Scott Cheloha wrote:
> Hi,
>
> The syncer thread is one of the last users of the lbolt (lightning
> bolt!) sleep channel.
>
> If we add a syncer-specific sleep channel (syncer_chan) and do a bit
> of time math we can replicate the current behavior and
Here is my try to extend ip(4) to also document struct ip_mreqn.
Not sure what is the best way to document the option to use either struct
ip_mreq or struct ip_mreqn with IP_ADD_MEMBERSHIP.
--
:wq Claudio
Index: ip.4
===
RCS file:
Hi,
I want to isolate statclock() from hardclock(9). This will simplify
the logic in my WIP dynamic clock interrupt framework.
Currently, if stathz is zero, we call statclock() from within
hardclock(9). It looks like this (see sys/kern/kern_clock.c):
void
hardclock(struct clockframe *frame)
{
On Wed, Jan 06, 2021 at 10:48:58PM +0100, Marcus Glocker wrote:
[...]
> The implementation as such looks fine to me.
> But I quickly gave the diff a spin before on amd64 using my PS
> controller, and the result is not what I would expect.
>
> With uhid, I can access the controller on
On Thu, Jan 07, 2021 at 04:56:14PM +0100, Denis Fondras wrote:
> Le Thu, Jan 07, 2021 at 12:03:54PM +0100, Hiltjo Posthuma a écrit :
> > Hi Denis,
> >
> > I like this feature. For example it would be useful for using relayd as a
> > reverse-proxy to forward it to an internal network running a
On Thu, Jan 07, 2021 at 11:16:16PM +, Adam Barth wrote:
> Previously, this code was passing string constants to functions that did
> not declare their parameters as const. After this patch, the functions now
> declare that they do not modify these arguments, making it safe to pass
> string
On Fri, 08 Jan 2021 00:29:32 +0100, Theo Buehler wrote:
> Thanks. Unfortunately the patch was mangled by your MUA (line wrapping
> and expanded tabs).
>
> Below is a version that applies.
OK millert@ as well.
- todd
Previously, this code was passing string constants to functions that did
not declare their parameters as const. After this patch, the functions now
declare that they do not modify these arguments, making it safe to pass
string constants.
diff --git lib/libc/gen/fts.c lib/libc/gen/fts.c
index
Thanks so much! This is my first patch for OpenBSD, and I don't quite have
the workflow debugged yet.
Adam
On Thu, Jan 7, 2021 at 11:29 PM Theo Buehler wrote:
> On Thu, Jan 07, 2021 at 11:16:16PM +, Adam Barth wrote:
> > Previously, this code was passing string constants to functions
On Thu, Jan 07, 2021 at 09:37:58PM +0100, Mark Kettenis wrote:
> > Date: Thu, 7 Jan 2021 11:15:41 -0600
> > From: Scott Cheloha
> >
> > Hi,
> >
> > I want to isolate statclock() from hardclock(9). This will simplify
> > the logic in my WIP dynamic clock interrupt framework.
> >
> > Currently,
Le Thu, Jan 07, 2021 at 12:03:54PM +0100, Hiltjo Posthuma a écrit :
> Hi Denis,
>
> I like this feature. For example it would be useful for using relayd as a
> reverse-proxy to forward it to an internal network running a httpd with some
> service. Then the path can be stripped without having to
When bgpd generates an UPDATE to update or withdraw prefixes it does this
from rde_generate_updates() and then decends into up_generate_update().
Now there is up_test_update() that checks if a new prefix is actually OK
to be distributed. It checks things for route reflectors and the common
23 matches
Mail list logo
