cisco have a tweak to gre that splits the key field into a 24bit
key and 8 bit flow id. the key still identifies the network, but
the flow id represents the traffic inside the tunnel.
i figured since gre has it's own special ioctls for configuring the
keepalives, it could grow another small one to
On Sun, Feb 18, 2018 at 07:42:10PM -0600, Scott Cheloha wrote:
> On Sun, Feb 18, 2018 at 02:44:43PM -0800, Mike Larkin wrote:
> > On Sun, Feb 18, 2018 at 12:00:01PM -0600, Scott Cheloha wrote:
> > > Hi,
> > >
> > > Is it bad if the olatch counts up if the host's wall clock
> > > is set backward?
On Sun, Feb 18, 2018 at 02:44:43PM -0800, Mike Larkin wrote:
> On Sun, Feb 18, 2018 at 12:00:01PM -0600, Scott Cheloha wrote:
> > Hi,
> >
> > Is it bad if the olatch counts up if the host's wall clock
> > is set backward? Or if the olatch makes a big jump for
> > the same reason?
> >
> > Serious
this is a simple port of the tunneldf stuff to vxlan.
ok?
Index: if_vxlan.c
===
RCS file: /cvs/src/sys/net/if_vxlan.c,v
retrieving revision 1.66
diff -u -p -r1.66 if_vxlan.c
--- if_vxlan.c 22 Jan 2018 09:05:06 - 1.66
+++ if
On Sun, Feb 18, 2018 at 12:00:01PM -0600, Scott Cheloha wrote:
> Hi,
>
> Is it bad if the olatch counts up if the host's wall clock
> is set backward? Or if the olatch makes a big jump for
> the same reason?
>
> Serious question: I don't have any EPT hardware to test
> this (sorry).
>
> While h
Yeah, you are right. And, I am not telling anyone to do that for me.
I had asked just because of curiosity that how a non-pledged process
has some fixed pledge value.
I thought someone already knows about that.
Thank you for help :)
On Mon, Feb 19, 2018 at 3:02 AM, Stuart Henderson wrote:
> O
On February 18, 2018 6:37:52 PM GMT+01:00, Robert Peichaer
wrote:
>On Sun, Feb 18, 2018 at 12:36:43PM +0100, Klemens Nanni wrote:
>> On Tue, Nov 21, 2017 at 08:30:25PM +0100, Klemens Nanni wrote:
>> > On Sun, Nov 12, 2017 at 10:43:46PM +0100, Klemens Nanni wrote:
>> > > On Sun, Nov 12, 2017 at
On 2018/02/18 20:05, Neeraj Pal wrote:
> On Sun, Feb 18, 2018 at 6:21 PM, Stuart Henderson
> wrote:
> > On 2018/02/18 12:36, Neeraj Pal wrote:
> >> I read kern_pledge.c file, but, I am not able to figure out the pledge
> >> bit value of a program which isn't using pledge() system call in
> >> use
Yeah, Stuart told me about PS_PLEDGE, sorry I don't know how I forgot.
And, yes, pledge_xbit is nothing in the kernel, I just added a random
string for output.
Thanks for clarification Otto.
So, just for printing out values, I have changed sched_bsd.c code.
# diff -u sched_bsd.c sys/kern/sched_
Hi,
Is it bad if the olatch counts up if the host's wall clock
is set backward? Or if the olatch makes a big jump for
the same reason?
Serious question: I don't have any EPT hardware to test
this (sorry).
While here, it looks like we can (a) roll the olatch-writing
parts of i8253_do_readback in
On Sun, Feb 18, 2018 at 12:36:43PM +0100, Klemens Nanni wrote:
> On Tue, Nov 21, 2017 at 08:30:25PM +0100, Klemens Nanni wrote:
> > On Sun, Nov 12, 2017 at 10:43:46PM +0100, Klemens Nanni wrote:
> > > On Sun, Nov 12, 2017 at 09:04:22PM +, Robert Peichaer wrote:
> > > > Hmm. I see.
> > > >
> >
Hi Bob,
I was going to suggest Stripe, but it seems they have very recently
discontinued support for Bitcoin. You can read their reasons why here:
https://stripe.com/blog/ending-bitcoin-support
Perhaps the problems with BitPay are not due to suspected fraud / money
laundering, but other business
On 2018/02/18 16:25, Stuart Henderson wrote:
> On 2018/02/18 21:19, Neeraj Pal wrote:
> > yeah, but I am asking about pledge_xbit (pledge value of any process
> > in hex). See output:
> >
> > process name: pltestnopledge(no pledge)ps_flags:
> > 101007 kern_exec: 10 pid: 66
On 2018/02/18 21:19, Neeraj Pal wrote:
> yeah, but I am asking about pledge_xbit (pledge value of any process
> in hex). See output:
>
> process name: pltestnopledge(no pledge)ps_flags:
> 101007 kern_exec: 10 pid: 66364 pledge_xbit: 8009588f
>
> process name: pltest(wit
On Sun, Feb 18, 2018 at 09:19:12PM +0530, Neeraj Pal wrote:
> yeah, but I am asking about pledge_xbit (pledge value of any process
> in hex). See output:
>
> process name: pltestnopledge(no pledge)ps_flags:
> 101007 kern_exec: 10 pid: 66364 pledge_xbit: 8009588f
>
> pr
This diff adds support for "legacy" (pre-11n) modes to MiRa,
and makes the following drivers use MiRa in non-11n modes:
iwn(4), iwm(4), athn(4), wpi(4)
This is an extension to the MiRa paper which I made up.
There is no science behind this whatsoever :-)
The way I have implemented it is to put
yeah, but I am asking about pledge_xbit (pledge value of any process
in hex). See output:
process name: pltestnopledge(no pledge)ps_flags:
101007 kern_exec: 10 pid: 66364 pledge_xbit: 8009588f
process name: pltest(with pledge("stdio",NULL)) ps_flags: 101007
kern_ex
On 2018/02/18 20:00, Neeraj Pal wrote:
> Okay. So, you told me that If I need to check which process pledge
> what, then I need to first check PS_PLEDGE bit
> is set or not because it indicates whether a pledge called or not in a
> process.
>
> But, what I asked is, if the pledge is not even call
Okay. So, you told me that If I need to check which process pledge
what, then I need to first check PS_PLEDGE bit
is set or not because it indicates whether a pledge called or not in a process.
But, what I asked is, if the pledge is not even called in userspace
code of any process, let's take an e
On Sun, Feb 18, 2018 at 11:51:14AM +1100, Jason Tubnor wrote:
> Hi,
>
> In some instances, we have found that where softdep has been placed on file
> systems that are used as part of the KARL process, incomplete writes have
> occurred (not committed to storage correctly) prior to reboot. Files
>
On Sun, Feb 18, 2018 at 6:21 PM, Stuart Henderson wrote:
> On 2018/02/18 12:36, Neeraj Pal wrote:
>> I read kern_pledge.c file, but, I am not able to figure out the pledge
>> bit value of a program which isn't using pledge() system call in
>> user-space code.
>> Because even after not using pledge
Okay. So, you told me that If I need to check which process pledge
what, then I need to first check PS_PLEDGE bit
is set or not because it indicates whether a pledge called or not in a process.
But, what I asked is, if the pledge is not even called in userspace
code of any process, let's take an e
On Mon, Jan 29, 2018 at 12:30:58PM +0100, Stefan Sperling wrote:
> On Mon, Jan 29, 2018 at 11:12:09AM +0100, Stefan Sperling wrote:
> > Here's what the diff you sent looks like if generated with 'cvs diff -up':
>
> It looks like you got most/all of these changes from Linux ath5k?
> Please be very
On 2018/02/18 12:36, Neeraj Pal wrote:
> I read kern_pledge.c file, but, I am not able to figure out the pledge
> bit value of a program which isn't using pledge() system call in
> user-space code.
> Because even after not using pledge() system call in user-space,
> still, every process has some de
On Tue, Nov 21, 2017 at 08:30:25PM +0100, Klemens Nanni wrote:
> On Sun, Nov 12, 2017 at 10:43:46PM +0100, Klemens Nanni wrote:
> > On Sun, Nov 12, 2017 at 09:04:22PM +, Robert Peichaer wrote:
> > > Hmm. I see.
> > >
> > > The {add,del,no,pre}_path functions are in ksh.kshrc since when it was
25 matches
Mail list logo
