| To: | "David S. Miller" <davem@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] minor socket ioctl cleanup for 2.5.30 |
| From: | Matthew Wilcox <willy@xxxxxxxxxx> |
| Date: | Thu, 8 Aug 2002 17:07:20 +0100 |
| Cc: | jmorris@xxxxxxxxxxxxxxxx, kuznet@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, willy@xxxxxxxxxx |
| In-reply-to: | <20020808.083320.100990288.davem@xxxxxxxxxx>; from davem@xxxxxxxxxx on Thu, Aug 08, 2002 at 08:33:20AM -0700 |
| References: | <Mutt.LNX.4.44.0208081018410.16830-100000@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20020808.083320.100990288.davem@xxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5.1i |
On Thu, Aug 08, 2002 at 08:33:20AM -0700, David S. Miller wrote: > From: James Morris <jmorris@xxxxxxxxxxxxxxxx> > Date: Thu, 8 Aug 2002 10:24:19 +1000 (EST) > > Suggested by Matthew Wilcox, the patch below consolidates FIOSETOWN etc. > ioctl handling into the socket layer, making it common for all sockets. > > Do we really want to do this? What if some socket family either > doesn't want to support it or wants to handle it differently? I rather think we do. It's analagous to saying "What if some filesystem either doesn't want to support it or wants to handle it differently?" -- tough! This is unix and filesystems (socket families) support this. have you read forsyth's paper "Sending UNIX to the Fat Farm"? http://www.caldo.demon.co.uk/doc/taste.pdf Section 3.3 is relevant here ... though I think you'll find great amusement in his other criticisms of solaris. -- Revolutions do not require corporate support. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] minor socket ioctl cleanup for 2.5.30, David S. Miller |
|---|---|
| Next by Date: | Re: [PATCH] minor socket ioctl cleanup for 2.5.30, kuznet |
| Previous by Thread: | Re: [PATCH] minor socket ioctl cleanup for 2.5.30, David S. Miller |
| Next by Thread: | Re: [PATCH] minor socket ioctl cleanup for 2.5.30, kuznet |
| Indexes: | [Date] [Thread] [Top] [All Lists] |