On Tue, Dec 15, 2015 at 7:53 AM, Andrew Vagin wrote:
> On Mon, Dec 14, 2015 at 02:38:06PM -0800, Andy Lutomirski wrote:
>> On Dec 13, 2015 11:52 PM, "Andrew Vagin" wrote:
>> >
>> > On Thu, Dec 03, 2015 at 03:20:30PM -0800, Andy Lutomirski wrote:
>> > > On Tue, Nov 24, 2015 at 7:18 AM, Andrew
On Mon, Dec 14, 2015 at 02:38:06PM -0800, Andy Lutomirski wrote:
> On Dec 13, 2015 11:52 PM, "Andrew Vagin" wrote:
> >
> > On Thu, Dec 03, 2015 at 03:20:30PM -0800, Andy Lutomirski wrote:
> > > On Tue, Nov 24, 2015 at 7:18 AM, Andrew Vagin
> > > wrote:
> > > > Hello Everybody,
> > > >
> > > >
On Tue, Dec 15, 2015 at 7:53 AM, Andrew Vagin wrote:
> On Mon, Dec 14, 2015 at 02:38:06PM -0800, Andy Lutomirski wrote:
>> On Dec 13, 2015 11:52 PM, "Andrew Vagin" wrote:
>> >
>> > On Thu, Dec 03, 2015 at 03:20:30PM -0800, Andy Lutomirski wrote:
>> > >
On Mon, Dec 14, 2015 at 02:38:06PM -0800, Andy Lutomirski wrote:
> On Dec 13, 2015 11:52 PM, "Andrew Vagin" wrote:
> >
> > On Thu, Dec 03, 2015 at 03:20:30PM -0800, Andy Lutomirski wrote:
> > > On Tue, Nov 24, 2015 at 7:18 AM, Andrew Vagin
> > >
On Dec 13, 2015 11:52 PM, "Andrew Vagin" wrote:
>
> On Thu, Dec 03, 2015 at 03:20:30PM -0800, Andy Lutomirski wrote:
> > On Tue, Nov 24, 2015 at 7:18 AM, Andrew Vagin wrote:
> > > Hello Everybody,
> > >
> > > Sorry for the long delay. I wanted to resurrect this thread.
> > >
> > > Andy suggested
On Fri, Dec 04, 2015 at 12:43:29AM +0100, Arnd Bergmann wrote:
> On Thursday 03 December 2015 15:20:30 Andy Lutomirski wrote:
> > > * Netlink is designed for such type of workloads. It allows to expand
> > > the interface and save backward compatibility. It allows to generates
> > > packets
On Fri, Dec 04, 2015 at 12:43:29AM +0100, Arnd Bergmann wrote:
> On Thursday 03 December 2015 15:20:30 Andy Lutomirski wrote:
> > > * Netlink is designed for such type of workloads. It allows to expand
> > > the interface and save backward compatibility. It allows to generates
> > > packets
On Dec 13, 2015 11:52 PM, "Andrew Vagin" wrote:
>
> On Thu, Dec 03, 2015 at 03:20:30PM -0800, Andy Lutomirski wrote:
> > On Tue, Nov 24, 2015 at 7:18 AM, Andrew Vagin wrote:
> > > Hello Everybody,
> > >
> > > Sorry for the long delay. I wanted to
On Thu, Dec 03, 2015 at 03:20:30PM -0800, Andy Lutomirski wrote:
> On Tue, Nov 24, 2015 at 7:18 AM, Andrew Vagin wrote:
> > Hello Everybody,
> >
> > Sorry for the long delay. I wanted to resurrect this thread.
> >
> > Andy suggested to create a new syscall instead of using netlink
> > interface.
On Thu, Dec 03, 2015 at 03:20:30PM -0800, Andy Lutomirski wrote:
> On Tue, Nov 24, 2015 at 7:18 AM, Andrew Vagin wrote:
> > Hello Everybody,
> >
> > Sorry for the long delay. I wanted to resurrect this thread.
> >
> > Andy suggested to create a new syscall instead of using
On Thursday 03 December 2015 15:20:30 Andy Lutomirski wrote:
> > * Netlink is designed for such type of workloads. It allows to expand
> > the interface and save backward compatibility. It allows to generates
> > packets with a different set of parameters.
> > * If we use a file descriptor, we
On Tue, Nov 24, 2015 at 7:18 AM, Andrew Vagin wrote:
> Hello Everybody,
>
> Sorry for the long delay. I wanted to resurrect this thread.
>
> Andy suggested to create a new syscall instead of using netlink
> interface.
>> Would it make more sense to have a new syscall instead? You could
>> even
On Tue, Nov 24, 2015 at 7:18 AM, Andrew Vagin wrote:
> Hello Everybody,
>
> Sorry for the long delay. I wanted to resurrect this thread.
>
> Andy suggested to create a new syscall instead of using netlink
> interface.
>> Would it make more sense to have a new syscall
On Thursday 03 December 2015 15:20:30 Andy Lutomirski wrote:
> > * Netlink is designed for such type of workloads. It allows to expand
> > the interface and save backward compatibility. It allows to generates
> > packets with a different set of parameters.
> > * If we use a file descriptor, we
Hello Everybody,
Sorry for the long delay. I wanted to resurrect this thread.
Andy suggested to create a new syscall instead of using netlink
interface.
> Would it make more sense to have a new syscall instead? You could
> even still use nlattr formatting for the syscall results.
I tried to
Hello Everybody,
Sorry for the long delay. I wanted to resurrect this thread.
Andy suggested to create a new syscall instead of using netlink
interface.
> Would it make more sense to have a new syscall instead? You could
> even still use nlattr formatting for the syscall results.
I tried to
On Wed, Jul 8, 2015 at 3:49 PM, Andrey Vagin wrote:
> 2015-07-08 20:39 GMT+03:00 Andy Lutomirski :
>> On Wed, Jul 8, 2015 at 9:10 AM, Andrew Vagin wrote:
>>>
>>> As far as I understand, socket_diag doesn't have this problem, becaus
>>> each socket has a link on a namespace where it was created.
2015-07-08 20:39 GMT+03:00 Andy Lutomirski :
> On Wed, Jul 8, 2015 at 9:10 AM, Andrew Vagin wrote:
>> On Tue, Jul 07, 2015 at 08:56:37AM -0700, Andy Lutomirski wrote:
>>> On Tue, Jul 7, 2015 at 8:43 AM, Andrew Vagin wrote:
>>> > On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
On Wed, Jul 8, 2015 at 9:10 AM, Andrew Vagin wrote:
> On Tue, Jul 07, 2015 at 08:56:37AM -0700, Andy Lutomirski wrote:
>> On Tue, Jul 7, 2015 at 8:43 AM, Andrew Vagin wrote:
>> > On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
>> >> On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin
On Tue, Jul 07, 2015 at 08:56:37AM -0700, Andy Lutomirski wrote:
> On Tue, Jul 7, 2015 at 8:43 AM, Andrew Vagin wrote:
> > On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
> >> On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
> >> > Currently we use the proc file system, where
On Tue, Jul 07, 2015 at 08:56:37AM -0700, Andy Lutomirski wrote:
On Tue, Jul 7, 2015 at 8:43 AM, Andrew Vagin ava...@odin.com wrote:
On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin ava...@openvz.org wrote:
Currently we use the
On Wed, Jul 8, 2015 at 9:10 AM, Andrew Vagin ava...@odin.com wrote:
On Tue, Jul 07, 2015 at 08:56:37AM -0700, Andy Lutomirski wrote:
On Tue, Jul 7, 2015 at 8:43 AM, Andrew Vagin ava...@odin.com wrote:
On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
On Mon, Jul 6, 2015 at
2015-07-08 20:39 GMT+03:00 Andy Lutomirski l...@amacapital.net:
On Wed, Jul 8, 2015 at 9:10 AM, Andrew Vagin ava...@odin.com wrote:
On Tue, Jul 07, 2015 at 08:56:37AM -0700, Andy Lutomirski wrote:
On Tue, Jul 7, 2015 at 8:43 AM, Andrew Vagin ava...@odin.com wrote:
On Mon, Jul 06, 2015 at
On Wed, Jul 8, 2015 at 3:49 PM, Andrey Vagin ava...@openvz.org wrote:
2015-07-08 20:39 GMT+03:00 Andy Lutomirski l...@amacapital.net:
On Wed, Jul 8, 2015 at 9:10 AM, Andrew Vagin ava...@odin.com wrote:
As far as I understand, socket_diag doesn't have this problem, becaus
each socket has a
On 7/7/15 10:27 AM, Andy Lutomirski wrote:
On Tue, Jul 7, 2015 at 9:25 AM, Arnaldo Carvalho de Melo
wrote:
Em Tue, Jul 07, 2015 at 06:43:46PM +0300, Andrew Vagin escreveu:
On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
On 7/7/15 10:24 AM, Andy Lutomirski wrote:
On Tue, Jul 7, 2015 at 9:17 AM, David Ahern wrote:
On 7/7/15 9:56 AM, Andy Lutomirski wrote:
Netlink is fine for these use cases (if they were related to the
netns, not the pid ns or user ns), and it works. It's still tedious
-- I bet that if you
On Tue, Jul 7, 2015 at 9:25 AM, Arnaldo Carvalho de Melo
wrote:
> Em Tue, Jul 07, 2015 at 06:43:46PM +0300, Andrew Vagin escreveu:
>> On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
>> > On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
>> > Would it make more sense to have a
Em Tue, Jul 07, 2015 at 06:43:46PM +0300, Andrew Vagin escreveu:
> On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
> > On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
> > Would it make more sense to have a new syscall instead? You could
> > even still use nlattr formatting
On Tue, Jul 7, 2015 at 9:17 AM, David Ahern wrote:
> On 7/7/15 9:56 AM, Andy Lutomirski wrote:
>>
>> Netlink is fine for these use cases (if they were related to the
>> netns, not the pid ns or user ns), and it works. It's still tedious
>> -- I bet that if you used a syscall, the user code would
On 7/7/15 9:56 AM, Andy Lutomirski wrote:
Netlink is fine for these use cases (if they were related to the
netns, not the pid ns or user ns), and it works. It's still tedious
-- I bet that if you used a syscall, the user code would be
considerable shorter, though. :)
How would this be a
On Tue, Jul 7, 2015 at 8:43 AM, Andrew Vagin wrote:
> On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
>> On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
>> > Currently we use the proc file system, where all information are
>> > presented in text files, what is convenient for
On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
> On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
> > Currently we use the proc file system, where all information are
> > presented in text files, what is convenient for humans. But if we need
> > to get information about
On Tue, Jul 7, 2015 at 9:17 AM, David Ahern dsah...@gmail.com wrote:
On 7/7/15 9:56 AM, Andy Lutomirski wrote:
Netlink is fine for these use cases (if they were related to the
netns, not the pid ns or user ns), and it works. It's still tedious
-- I bet that if you used a syscall, the user
On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin ava...@openvz.org wrote:
Currently we use the proc file system, where all information are
presented in text files, what is convenient for humans. But if we need
to get information
Em Tue, Jul 07, 2015 at 06:43:46PM +0300, Andrew Vagin escreveu:
On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin ava...@openvz.org wrote:
Would it make more sense to have a new syscall instead? You could
even still use nlattr
On Tue, Jul 7, 2015 at 8:43 AM, Andrew Vagin ava...@odin.com wrote:
On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin ava...@openvz.org wrote:
Currently we use the proc file system, where all information are
presented in text files,
On 7/7/15 9:56 AM, Andy Lutomirski wrote:
Netlink is fine for these use cases (if they were related to the
netns, not the pid ns or user ns), and it works. It's still tedious
-- I bet that if you used a syscall, the user code would be
considerable shorter, though. :)
How would this be a
On Tue, Jul 7, 2015 at 9:25 AM, Arnaldo Carvalho de Melo
a...@kernel.org wrote:
Em Tue, Jul 07, 2015 at 06:43:46PM +0300, Andrew Vagin escreveu:
On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin ava...@openvz.org wrote:
Would it
On 7/7/15 10:24 AM, Andy Lutomirski wrote:
On Tue, Jul 7, 2015 at 9:17 AM, David Ahern dsah...@gmail.com wrote:
On 7/7/15 9:56 AM, Andy Lutomirski wrote:
Netlink is fine for these use cases (if they were related to the
netns, not the pid ns or user ns), and it works. It's still tedious
-- I
On 7/7/15 10:27 AM, Andy Lutomirski wrote:
On Tue, Jul 7, 2015 at 9:25 AM, Arnaldo Carvalho de Melo
a...@kernel.org wrote:
Em Tue, Jul 07, 2015 at 06:43:46PM +0300, Andrew Vagin escreveu:
On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
On Mon, Jul 6, 2015 at 1:47 AM, Andrey
On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
> Currently we use the proc file system, where all information are
> presented in text files, what is convenient for humans. But if we need
> to get information about processes from code (e.g. in C), the procfs
> doesn't look so cool.
>
> From
Currently we use the proc file system, where all information are
presented in text files, what is convenient for humans. But if we need
to get information about processes from code (e.g. in C), the procfs
doesn't look so cool.
>From code we would prefer to get information in binary format and to
Currently we use the proc file system, where all information are
presented in text files, what is convenient for humans. But if we need
to get information about processes from code (e.g. in C), the procfs
doesn't look so cool.
From code we would prefer to get information in binary format and to
On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin ava...@openvz.org wrote:
Currently we use the proc file system, where all information are
presented in text files, what is convenient for humans. But if we need
to get information about processes from code (e.g. in C), the procfs
doesn't look so
44 matches
Mail list logo