Re: horribly slow fsck_ffs pass1 performance

2011-04-02 Thread Otto Moerbeek
On Sat, Apr 02, 2011 at 01:45:36PM -0500, Amit Kulkarni wrote: > Hi, > > I am replying in a single email. > > I do a fsck once in a while, not regular. In the last 6-8 months I > might have done it about 5 times. And I did it multi-user the few > times I did it, but plan on doing it single user

A solo 2 meses de la Cumbre de Especialidades Juveniles Argentina

2011-04-02 Thread Novedades Feedback
Mail para ser visto con conexisn, si no puede verlo, click aqum [IMAGE] FeedBack [IMAGE] FeedBack Feedback, comunicacion en serio [IMAGE] [IMAGE] Mas Info: Email: i...@especialidadesjuveniles.com Web Site: www.especialidadesjuveniles.com Facebook: Especialidades Juveniles Argentina[IMAGE]

Re: Adding support for AI_FQDN to getaddrinfo(3)?

2011-04-02 Thread Damien Miller
On Sat, 2 Apr 2011, Damien Miller wrote: > AI_FQDN solves these problems quite nicely. It is also useful for web > browsers that face a similar problem (e.g. https://intranet/) but > getting them to adopt it might be more tricky. I'd love to see this get > deployed so we can use it in OpenSSH (whi

Re: relax gcc -Wsentinel checking

2011-04-02 Thread Mark Kettenis
> Date: Sat, 2 Apr 2011 11:13:05 + > From: Miod Vallat > > The -Wsentinel warning is supposed to complain when the last argument in > a call to a function which has __attribute__((sentinel)) is not a NULL > pointer. > > However, the current implementation of the check in gcc 3 and gcc 4 will

Re: horribly slow fsck_ffs pass1 performance

2011-04-02 Thread Kevin Chadwick
On Sat, 02 Apr 2011 17:46:51 +0200 Benny Lofgren wrote: > It must mean they don't trust their own file > systems, which frankly I find a bit unsettling... I'd rather use a file > system that's been field proven for decades than use something thats > just come out of the experimenting shop. Hopef

Re: horribly slow fsck_ffs pass1 performance

2011-04-02 Thread Stuart Henderson
On 2011/04/02 13:45, Amit Kulkarni wrote: > > I do a fsck once in a while, not regular. In the last 6-8 months I > might have done it about 5 times. And I did it multi-user the few > times I did it, but plan on doing it single user in future and I do > plan to do it monthly. After seeing the messa

Re: horribly slow fsck_ffs pass1 performance

2011-04-02 Thread Amit Kulkarni
Hi, I am replying in a single email. I do a fsck once in a while, not regular. In the last 6-8 months I might have done it about 5 times. And I did it multi-user the few times I did it, but plan on doing it single user in future and I do plan to do it monthly. After seeing the messages when you f

Re: remove bufqs from vnds

2011-04-02 Thread Kenneth R Westerback
On Sat, Apr 02, 2011 at 01:58:22PM +, Thordur Bjornsson wrote: > Hi, > > So, it doesn't make sense to have a bufq for vnds. > > The disk that stores the image backing the vnd has it's own bufq > ofcourse and what happens is that vnd puts a buf on it's bufq, > which is promptly removed when

ata.c dma_alloc()

2011-04-02 Thread Kenneth R Westerback
Yet another driver that probably wouldn't like big mem. ok? Ken Index: dev/ata/ata.c === RCS file: /cvs/src/sys/dev/ata/ata.c,v retrieving revision 1.30 diff -u -p -r1.30 ata.c --- dev/ata/ata.c 23 Jul 2010 07:47:12 -

mbuf diff that affects IPSEC setups

2011-04-02 Thread Bret S. Lambert
Clean up the mbuf code a bit by collecting common code to split an individual mbuf, and rework those functions that need that to be wrappers around that. This impacts almost exclusively IPSEC mbuf usage, so if you have these setups, please ensure that this doesn't break those. - Bret Index: kern

Re: horribly slow fsck_ffs pass1 performance

2011-04-02 Thread Benny Lofgren
On 2011-04-01 19.03, Amit Kulkarni wrote: > Thank you Arthur and the team for a very fast turnaround! Thank you > for reducing the pain. I will schedule a fsck every month or so, > knowing it won't screw up anything and be done really quick. Why "schedule" fsck runs at all? The file system code is

Re: atascsi dma_alloc() - make atascsi play nicer with bigmem

2011-04-02 Thread Thordur Bjornsson
On Sat, Apr 02, 2011 at 09:15:37AM -0400, Kenneth R Westerback wrote: > Another driver malloc'ing and passing potentially dma unsafe memory > to do i/o into. > > ok? yub > > Ken > > Index: atascsi.c > === > RCS file: /cvs/src/s

Re: horribly slow fsck_ffs pass1 performance

2011-04-02 Thread Benny Lofgren
On 2011-04-01 21.48, Amit Kulkarni wrote: >> And jumping up and down after a first successful test is not a sound >> engineering principle either. [...stuff deleted...] > It turns out that I had extracted into the default firefox download > location (/home/amit/downloads I forgot exactly where) all

fast local address lookup in ip_input

2011-04-02 Thread Henning Brauer
so now that the loopback link1 crap is out of the way - use the rb tree for local address lookup in ip_input instead of traversing the list of interfaces traversing the list of addresses on them linearily. this needs heavy testing. last not least somebody please throw this on his rarpd server and

Re: remove bufqs from vnds

2011-04-02 Thread David Gwynne
ok On 02/04/2011, at 11:58 PM, Thordur Bjornsson wrote: > Hi, > > So, it doesn't make sense to have a bufq for vnds. > > The disk that stores the image backing the vnd has it's own bufq > ofcourse and what happens is that vnd puts a buf on it's bufq, > which is promptly removed when we call vnd

remove bufqs from vnds

2011-04-02 Thread Thordur Bjornsson
Hi, So, it doesn't make sense to have a bufq for vnds. The disk that stores the image backing the vnd has it's own bufq ofcourse and what happens is that vnd puts a buf on it's bufq, which is promptly removed when we call vndstart, followed by a call to strategy so the buf ends up almost immedi

Re: atascsi dma_alloc() - make atascsi play nicer with bigmem

2011-04-02 Thread David Gwynne
ok. On 02/04/2011, at 11:15 PM, Kenneth R Westerback wrote: > Another driver malloc'ing and passing potentially dma unsafe memory > to do i/o into. > > ok? > > Ken > > Index: atascsi.c > === > RCS file: /cvs/src/sys/dev/ata/a

pf and the ip checksum

2011-04-02 Thread Henning Brauer
pf keep updating the dreaded ip checksum. which is entirely pointless (except the quoted ip packet and its csum inside an icmp err) since we uncondtionally recalculate the checksum anyway in ip_output as well as in the bridge and the *&^%$(* pf route-to. so don't. Index: pf.c

atascsi dma_alloc() - make atascsi play nicer with bigmem

2011-04-02 Thread Kenneth R Westerback
Another driver malloc'ing and passing potentially dma unsafe memory to do i/o into. ok? Ken Index: atascsi.c === RCS file: /cvs/src/sys/dev/ata/atascsi.c,v retrieving revision 1.101 diff -u -p -r1.101 atascsi.c --- atascsi.c

Re: relax gcc -Wsentinel checking

2011-04-02 Thread Paul Irofti
On Sat, Apr 02, 2011 at 11:13:05AM +, Miod Vallat wrote: > The -Wsentinel warning is supposed to complain when the last argument in > a call to a function which has __attribute__((sentinel)) is not a NULL > pointer. > > However, the current implementation of the check in gcc 3 and gcc 4 will >

Re: netinet6 bread crumbs

2011-04-02 Thread Thordur Bjornsson
On Sat, Apr 02, 2011 at 02:13:45PM +0200, Stefan Sperling wrote: > Feel free to ack or reject these individually. > > > Kill redundant offsetof definitions. All of these files include sys/param.h. Those look fine. > Index: in6.c >

Re: kill loopback link1 wankery

2011-04-02 Thread Claudio Jeker
On Sat, Apr 02, 2011 at 10:56:06PM +1000, David Gwynne wrote: > all the things i can imagine using this for, i can do with pf features. > > ok. > Fine with me. > On 02/04/2011, at 10:49 PM, Henning Brauer wrote: > > > lo has that link1 wankery where it kind of replies to all addresses in > > t

Re: kill loopback link1 wankery

2011-04-02 Thread David Gwynne
all the things i can imagine using this for, i can do with pf features. ok. On 02/04/2011, at 10:49 PM, Henning Brauer wrote: > lo has that link1 wankery where it kind of replies to all addresses in > the subnet, except that it doesn't really - it is very halfbaked and > gets in the way. unless

kill loopback link1 wankery

2011-04-02 Thread Henning Brauer
lo has that link1 wankery where it kind of replies to all addresses in the subnet, except that it doesn't really - it is very halfbaked and gets in the way. unless somebody has a VERY convincing reason to keep this it'll be gone in a few. we'll be able to use the fast rb tree lookup in in_aiwithadd

Un-suscribe

2011-04-02 Thread David Medel Open Gmail
Un-suscribe

netinet6 bread crumbs

2011-04-02 Thread Stefan Sperling
Feel free to ack or reject these individually. Kill redundant offsetof definitions. All of these files include sys/param.h. Index: frag6.c === RCS file: /cvs/src/sys/netinet6/frag6.c,v retrieving revision 1.32 diff -u -p -r1.32 frag

Re: relax gcc -Wsentinel checking

2011-04-02 Thread Marco Peereboom
yes please! the casting of a NULL pointer is a pain in the butt and ugly. On Sat, Apr 02, 2011 at 11:13:05AM +, Miod Vallat wrote: > The -Wsentinel warning is supposed to complain when the last argument in > a call to a function which has __attribute__((sentinel)) is not a NULL > pointer. >

Fw: Segue em anexo relatorio orcamento.

2011-04-02 Thread Sandra Castro
[IMAGE] 1 anexos Relatorio-orcamento.pdf (142,0 kb) Segue em anexo o relatorio para orgamento. tenha um bom dia. __

Re: printf(1) null escape

2011-04-02 Thread Andres Perera
#include #define CMD "/usr/bin/printf" int main(void) { execle(CMD, CMD, "\\", NULL, (char *[]){"BROKEN", NULL}); } On Sat, Apr 2, 2011 at 4:48 AM, Andres Perera wrote: > > print_escape returns 1 even if it's on null, and the rest of the > prog just ignores null literals > > $ env -i sh

relax gcc -Wsentinel checking

2011-04-02 Thread Miod Vallat
The -Wsentinel warning is supposed to complain when the last argument in a call to a function which has __attribute__((sentinel)) is not a NULL pointer. However, the current implementation of the check in gcc 3 and gcc 4 will warn if the last argument is not explicitely declared as a pointer type,

printf(1) null escape

2011-04-02 Thread Andres Perera
print_escape returns 1 even if it's on null, and the rest of the prog just ignores null literals $ env -i sh -c '/usr/bin/printf \\' printf: unknown escape sequence `\' PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11R6/bin:/usr/local/bin diff -u -r1.17 printf.c --- printf.c27 Oct 2009 23:59:41 -0