summaryrefslogtreecommitdiff
path: root/external/bsd/top/dist/install-sh
diff options
context:
space:
mode:
authorrillig <rillig@NetBSD.org>2023-07-09 10:42:07 +0000
committerrillig <rillig@NetBSD.org>2023-07-09 10:42:07 +0000
commit61a832267cc5bff1a90f086bd56309a3a0671255 (patch)
tree6f663ed82c04970fa2f72561dc8eb6681e5f29fe /external/bsd/top/dist/install-sh
parentb2782b14a8e5066f0436d79a391ce49f9e782b76 (diff)
lint: remove redundant '#' after 'argument' in diagnosticsHEADtrunk
Diffstat (limited to 'external/bsd/top/dist/install-sh')
0 files changed, 0 insertions, 0 deletions
9-04 15:30:36 +0000'>2008-09-04Fix double free when i/o descriptor is violently closed. Bug waspooka introduced in rev 1.27. fix provided by Taylor R Campbell in lib/39353 2008-01-29Fix a weirdosity in the framebuf gotfb interface: hand bufferpooka ownership to the called routine instead of keeping it. This means that callees must now destroy the buffer once they are done with it. 2008-01-28Implement lazy contexts for file systems using puffs_mainloop().pooka Previously each request was executed on its own callcontext and switched to every time the request was being processed. Now requests borrow the mainloop context and switch only if/when they yield. This takes two context switches away from a file system request bringing down the typical amounts 2->0 (e.g. dtfs) and 4->2 (e.g. psshfs). The interfaces for manually executing requests changed a bit: puffs_dispatch_create() and puffs_dispatch_exec() must now be used. They are not tested, as nothing in-tree wants them and I doubt anyone else is really interested in them either. Also do some misc code cleanup related to execution contexts. The "work-in-progress checkpoint" committed over a year ago was starting to look slightly weed-infested. 2007-12-16* nuke puffs_cc_get{specific,usermount} for goodpooka * move prototypes for puffs_docc and puffs_dopufbuf into the public header, as they are should be exposed 2007-12-04Part 3/n of extensive changes to message handling:pooka Get rid of the original puffs_req(3) framework and use puffs_framebuf(3) instead for file system requests. It has the advantage of being suitable for transporting a distributed message passing protocol and therefore us being able to run the file system server on any host. Ok, puffs is not quite here yet: libpuffs needs to grow request routing support and the message contents need to be munged into a host independent format. Saying which format would be telling, but it might begin with an X, end in an L and have the 13th character in the middle. Keep an eye out for the sequels: Parts 3+m/n. 2007-12-04realloc() len+incr, not offset+incr. Makes space reservationpooka actually work properly. 2007-09-06document puffs_framev_framebuf_ccpromote()pooka 2007-09-06Give cmpframe() the ability to shortcircuit the comparison loop bypooka signalling back that the buffer under examination is not a response at all. 2007-09-01Add gotframe callback, which is called if an incoming frame matchespooka no outstanding request. 2007-08-25Pass usermount to errnotify, it might not be available there throughpooka other structures. CID 4496 2007-07-21Return -1 and errno from puffs_framev_enqueue_waitevent instead ofpooka a direct error value. 2007-07-20simplify send looppooka 2007-07-20Add puffs_framev_enqueue_waitevent, which waits for read/write/errorpooka events from an i/o descriptor. It yields until an event happens and continues execution when the event loop notices the event has happened. 2007-07-08g/c leftoverpooka 2007-07-08make notifyfunction optional and do not call removeonclose() ifpooka none is given. 2007-07-07Make puffs_framebuf better suited from environments with multiple sources:pooka * in addition add/remove, allow enable/disable, which can be used to control events for descriptors without having to remove all the data associated with them * add directsend/receive, which can be used to pass the same buffer from the caller to read/writeframe and back again * add flags to enqueue functions and allow urgent buffers to be processed as the next PDU 2007-05-20Introduce puffs_framev_framebuf_ccpromote, which can be used topooka turn a reference to puffs_framebuf in the file system from a cb/justsend operation to a cc wait, should the file system find itself desiring the result. 2007-05-20Change the signature of puffs_respcmp to return -1,0,1 for smaller,pooka equal, larger, respectively instead of 0/1 for non/equal. This will allow sorting the buffers for faster matching in libpuffs. While here, change the name from respcmp to framecmp, as that better reflects the purpose. NOTE! there is no obvious way to make compilation fail for file systems which may already be using this feature (although I don't think there are any outside our tree, as the feature is two weeks old). Nevertheless, non-updated file systems will fail very quickly. 2007-05-19Allocate buf in 4k chunks instead of 64k chunks. If we are seriouslypooka reclaiming and the network/server is slow, we might have thousands of buffers allocated at the same time causing the process to run out of vm space. Rate limiting the number of outstanding ops would be a nicer choice, but that requires more complex changes. 2007-05-16Add error parameter to puffs_framev_cb to signal if there is apooka result of if the function should just do resource cleanup. 2007-05-16switch the arbitrary default errno value for network i/o frompooka ECONNABORTED to ECONNRESET, which is at least a little bit better 2007-05-15Step 3 and currently final step of a more general purpose event loop:pooka support removal and addition of i/o file descriptors on the fly. * detect closed file descriptors * automatically free waiters of a dead file descriptor * give the file server the possibility to specify a callback which notifies of a dead file descriptor * move loop function to be a property of the mainloop instead of framebuf (doesn't change effective behaviour) * add the possibility to configure a timespec parameter which attempts to call the loop function periodically * move the event loop functions from the puffs_framebuf namespace to puffs_framev to differential between pure memory management functions 2007-05-12use size_t instead of int to calm over-eager lintpooka 2007-05-11Step 2 of general-purpose eventloop: get rid of puffs_framebuf_eventloop().pooka puffs_mainloop() now handles that functionality as well. 2007-05-11Step 1 in moving towards a general-purpose eventloop: allow thepooka framebuf event loop to take n i/o fd's as parameters and also allow dynamic add/remove of fd's. (not tested except for one fd, but more changes coming soon) 2007-05-09Remove the puffs_usermount argument from puffs_req_handle(). It canpooka be found from the other arguments and this way puffs_req_handle() is more symmetric with the other puffs_req() routines. 2007-05-06implement the conveniently-already-prototyped puffs_framebuf_remaining(),pooka which is just shorthand for tellsize() - telloff() 2007-05-06Remove the user-specified argument for the framebuf loop callback.pooka It can be generated through other means if it is desired. 2007-05-05Add puffs "frame buffers", which are an abstraction of the bufferingpooka and event handling mechanisms required in file servers with blocking I/O backends. puffs_framebuf is built on the concept of puffs_cc and uses those to multiplex execution where needed. File systems are required to implement three methods: * read frame * write frame * compare if frame is a response to the given one Memory management is provided by puffs_framebuf, but the file systems must still, of course, interpret the protocol and do e.g. byte order conversion. As always, puffs_framebuf is work in progress. Current users are mount_psshfs and mount_9p.