Ted Unangst wrote:
> > Keeping a buf with an error in the delayed write list would probably have
> > some
> > serious consequences. When would we ever remove it?
>
> Thought about this some more. The best approach may be to set a flag in
> the vnode that there was an IO error, and return that
On Thu, Jan 31, 2019 at 01:30:18PM -0500, Ted Unangst wrote:
> Anthony J. Bentley wrote:
> > Jason McIntyre writes:
> > > in the man page you have used Sq. that will make it mark up the same as
> > > it already does:
> > >
> > > (`*')
>
> fwiw there was already an existing sq in the man page. I
Anthony J. Bentley wrote:
> Jason McIntyre writes:
> > in the man page you have used Sq. that will make it mark up the same as
> > it already does:
> >
> > (`*')
fwiw there was already an existing sq in the man page. I only fixed the one
using literal single quotes.
> There's a difference:
On Thu, Jan 31, 2019 at 04:30:30PM +0100, Stefan Sperling wrote:
> On Thu, Jan 31, 2019 at 03:32:05PM +0100, Stefan Sperling wrote:
> > This diff completes noisefloor calibration code in our athn(4) driver.
> > Update default/min/max noisefloor values to those used by Linux.
> >
> > Tested on
Alex Holst wrote:
> Quoting Mark Kettenis (mark.kette...@xs4all.nl):
> > An accurate description would be that the percentage is actually the
> > percentage of "DMA-reachable" physical memory the buffer cache may
> > use. The minimum percentage is 5% and the maximum is 90%.
> >
> > But
On Thu, Jan 31, 2019 at 04:26:45PM -0500, Ted Unangst wrote:
> Instead, we note that the write failed and mark a flag in the vnode. Future
> calls to fsync will then return EIO when this flag is set. We clear the flag
> when the vnode is released.
Sounds reasonable.
OK bluhm@
> Index:
On Thu, Jan 31, 2019 at 11:02:05PM +0100, Juan Francisco Cantero Hurtado wrote:
> Works for me with an AR9271. I don't see differences.
Same here on AR9287 in a busy network with lots of clients, fwiw.
Resume/suspend, up/down, etc. all works as expected as without the diff.
Quoting Mark Kettenis (mark.kette...@xs4all.nl):
> An accurate description would be that the percentage is actually the
> percentage of "DMA-reachable" physical memory the buffer cache may
> use. The minimum percentage is 5% and the maximum is 90%.
>
> But documenting it like that needs an
Yes the queue is always that size.
Anton Lindqvist wrote:
> Comments? OK?
>
> Index: dev/wscons/wsevent.c
> ===
> RCS file: /cvs/src/sys/dev/wscons/wsevent.c,v
> retrieving revision 1.18
> diff -u -p -r1.18 wsevent.c
> ---
Hi,
This is not to suggest that the following would be relevant or needed:
Is there any any man page, or documents, slides, books or standards
specification documents regarding OpenBSD's memory model or memory
order considerations?
A marc.info misc@ or tech@ or Google search for query gives no
Comments? OK?
Index: dev/wscons/wsevent.c
===
RCS file: /cvs/src/sys/dev/wscons/wsevent.c,v
retrieving revision 1.18
diff -u -p -r1.18 wsevent.c
--- dev/wscons/wsevent.c19 Nov 2018 19:19:24 - 1.18
+++
On Wed, Jan 30, 2019 at 11:48:10AM +1000, David Gwynne wrote:
> mpls uses AF_MPLS routes with RTF_LOCAL set on them to know which tags
> are used as input for the mpe and mpw interfaces. setting this up
> currently goes through rt_ifa_add, but that has a couple of features
> that are undesirable
On Wed, Jan 30, 2019 at 01:56:04PM -0600, Scott Cheloha wrote:
> We need to tell ${CC} about b.o explicitly.
>
> ok?
>
> -Scott
>
> P.S. How was BSD $> or GNU $^ or an equivalent *not* standardized as
> an automatic variable? I get that it isn't a silver bullet, but in
> the relatively common
On Thu, Jan 31, 2019 at 03:10:53PM +0200, Lauri Tirkkonen wrote:
> On Wed, Jan 30 2019 20:32:50 -0500, Ted Unangst wrote:
> > Thanks for digging into this. I went ahead and committed your diff.
>
> Thanks for committing it.
>
> You know, having seen fgetln's allocation strategy and its usage of
> Date: Wed, 30 Jan 2019 22:31:31 +0100
> From: Patrick Wildt
>
> Hi,
>
> to boot a pinebook with softraid crypto there are three parts that need
> to be implemented, which this diff hopefully does well enough.
>
> First, our EFI bootloader so far only supports one disk, so we need to
> extend
On Wed, Jan 30 2019 20:32:50 -0500, Ted Unangst wrote:
> Thanks for digging into this. I went ahead and committed your diff.
Thanks for committing it.
You know, having seen fgetln's allocation strategy and its usage of the
stdio internals, I couldn't help but wonder if it's something that could
Contrary to other rules accepting a single port, this one only works
with unquoted numerical values.
Fix this by simply using the proper grammar; the impact is limited to
`divert-packet port $port' and easy to test:
$ printf 'pass divert-packet port %s\n' 80 '"443"' ftp '"domain"' |
This diff completes noisefloor calibration code in our athn(4) driver.
Update default/min/max noisefloor values to those used by Linux.
Tested on AR9280 on 2GHz and 5Ghz. Further tests are appreciated.
Index: ar5008.c
===
RCS file:
On Thu, Jan 31, 2019 at 03:32:05PM +0100, Stefan Sperling wrote:
> This diff completes noisefloor calibration code in our athn(4) driver.
> Update default/min/max noisefloor values to those used by Linux.
>
> Tested on AR9280 on 2GHz and 5Ghz. Further tests are appreciated.
jmc@ found out the
On Wed, Jan 30, 2019 at 10:39:11PM +0100, Klemens Nanni wrote:
> OK?
OK bluhm@
> Index: parse.y
> ===
> RCS file: /cvs/src/sbin/pfctl/parse.y,v
> retrieving revision 1.689
> diff -u -p -r1.689 parse.y
> --- parse.y 11 Jan 2019
On Wed, Jan 30, 2019 at 10:39:11PM +0100, Klemens Nanni wrote:
> Contrary to other rules accepting a single port, this one only works
> with unquoted numerical values.
Quoted numbers are accepted, I mixed it up when writing this mail.
> - | DIVERTPACKET PORT number {
> + |
21 matches
Mail list logo
