| To: | lists@xxxxxxxxxxxx (Ivan Passos) |
|---|---|
| Subject: | Re: [RFC-2] Configuring Synchronous Interfaces in Linux |
| From: | Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> |
| Date: | Tue, 5 Dec 2000 21:56:08 +0000 (GMT) |
| Cc: | alan@xxxxxxxxxxxxxxxxxxx (Alan Cox), linux-kernel@xxxxxxxxxxxxxxx (Linux Kernel List), netdev@xxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.10.10012051118140.1713-100000@xxxxxxxxxxxxxxxxx> from "Ivan Passos" at Dec 05, 2000 11:23:50 AM |
| Sender: | owner-netdev@xxxxxxxxxxx |
> Alan, what's the approach you'd feel more comfortable with: > - One ioctl that passes a pointer to a known structure in ifr.ifr_data as > its argument. > - Several ioctl's, one for each parameter, that pass only the specific > parameter new value as the argument. > > The former is good because it relies on a _single_ ioctl. However, every > time you change the ioctl structure you may lose backward compatibility. One ioctl with a set of subcommands seems to be quite common |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [RFC-2] Configuring Synchronous Interfaces in Linux, Peter Samuelson |
|---|---|
| Next by Date: | Re: [RFC] Configuring synchronous interfaces in Linux, Chris Wedgwood |
| Previous by Thread: | Re: [RFC-2] Configuring Synchronous Interfaces in Linux, Peter Samuelson |
| Next by Thread: | Re: [RFC-2] Configuring Synchronous Interfaces in Linux, Matthew G. Marsh |
| Indexes: | [Date] [Thread] [Top] [All Lists] |