Hello everyone
I've been using this diff for a few weeks and it works just fine,
just wanted to share my experience with it and thank Tobias.
Dear RMS; I've read that you are both a lisp and C developer. I cannot
get any contributors for the longstanding C 3d engine I work on as part
of my fully-free-software (including media) 3d game/architecture project.
I've been working on it alone for 10 years but now have branched into
supporting
Dear RMS;
I've read that you are both a lisp and C developer. I cannot get any
contributors for the longstanding C 3d engine I work on as part of my
fully-free-software (including media) 3d game/architecture project. I've been
working on it alone for 10 years but now have branched into
Alexander Bluhm wrote:
> During configuration there is usually some kind of lock, it happens
> rarely, and bugs are hard to trigger, especially on amd64 which
> guarantees some consistency. That's why it works.
>
> > Some times ago, I privately pointed this and proposed to modify if_flags
> >
On Fri, Oct 06, 2023 at 04:17:34PM +0300, Vitaliy Makkoveev wrote:
> On Fri, Oct 06, 2023 at 02:50:21PM +0200, Alexander Bluhm wrote:
> > On Fri, Oct 06, 2023 at 12:45:54PM +0300, Vitaliy Makkoveev wrote:
> > > On Thu, Oct 05, 2023 at 10:42:25PM +1000, David Gwynne wrote:
> > > > > On 5 Oct 2023,
On Fri, Oct 06, 2023 at 03:47:31PM +0300, Vitaliy Makkoveev wrote:
> On Fri, Oct 06, 2023 at 02:14:52PM +0200, Alexander Bluhm wrote:
> > > @@ -718,11 +743,13 @@ softclock(void *arg)
> > > softclock_process_tick_timeout(to, new);
> > > }
> > > tostat.tos_softclocks++;
> > > -
On Fri, Oct 06, 2023 at 02:14:52PM +0200, Alexander Bluhm wrote:
> On Fri, Oct 06, 2023 at 02:12:31PM +0300, Vitaliy Makkoveev wrote:
> > I reworked your diff for a little. At firts I use separate
> > softclock_thread_mpsafe() for mpsafe timers. I don't think we need to
> > bind this thread to the
On Fri, Oct 06, 2023 at 02:50:21PM +0200, Alexander Bluhm wrote:
> On Fri, Oct 06, 2023 at 12:45:54PM +0300, Vitaliy Makkoveev wrote:
> > On Thu, Oct 05, 2023 at 10:42:25PM +1000, David Gwynne wrote:
> > > > On 5 Oct 2023, at 21:50, Vitaliy Makkoveev wrote:
> > > >
> > > > I don't like this
On Fri, Oct 06, 2023 at 12:45:54PM +0300, Vitaliy Makkoveev wrote:
> On Thu, Oct 05, 2023 at 10:42:25PM +1000, David Gwynne wrote:
> > > On 5 Oct 2023, at 21:50, Vitaliy Makkoveev wrote:
> > >
> > > I don't like this unlocked if_flags check we have in ifq_start_task().
> > > Guess READ_ONCE() is
On Fri, Oct 06, 2023 at 02:14:52PM +0200, Alexander Bluhm wrote:
> > @@ -718,11 +743,13 @@ softclock(void *arg)
> > softclock_process_tick_timeout(to, new);
> > }
> > tostat.tos_softclocks++;
> > - needsproc = !CIRCQ_EMPTY(_proc);
> > - mtx_leave(_mutex);
> > -
> >
On Fri, Oct 06, 2023 at 02:12:31PM +0300, Vitaliy Makkoveev wrote:
> I reworked your diff for a little. At firts I use separate
> softclock_thread_mpsafe() for mpsafe timers. I don't think we need to
> bind this thread to the primary CPU.
I also think a separate thread is better. Makes no sense
On Thu, Oct 05, 2023 at 10:07:24PM +0300, Vitaliy Makkoveev wrote:
> On Thu, Oct 05, 2023 at 11:09:52AM -0500, Scott Cheloha wrote:
> > On Thu, Oct 05, 2023 at 12:57:24AM +0200, Alexander Bluhm wrote:
> > >
> > > This is a first step to unlock TCP syn cache. The timer function
> > > is
[this change was lost between others and private mails...]
Passphrases must not be empty or else volume creation/unlock fails:
# bioctl -cC -lvnd0a softraid0
New passphrase:
Re-type passphrase:
bioctl: bcrypt_pbkdf failed
[-p passfile] already says "invalid
Thanks for attention at this. But now I don't like this diff. It
silently drops stuck packets, so `ph_cookie' linked data could leak.
Obviously wg_peer_destroy() and wg_qstart() should be fixed in different
way.
On Thu, Oct 05, 2023 at 10:42:25PM +1000, David Gwynne wrote:
>
>
> > On 5 Oct
14 matches
Mail list logo
